Proca release script

[marcinkoziej]

It would be great to be able to deloy proca server in a way where we get a executable with additional tools like "seed the db" "reset admin password" and so on built in. Right now the Elixir release mechanism creates this kind of convoluted script in rel/proca/bin/proca - which is not something I'd like to hack. There is also a Bakeware project that is an alternative - bundles all the server into one executable file. I need to see how it looks like..

Ideally after you install a proca release somewhere, you can run:

• proca start
• proca remote
• proca rpc
• proca admin-password-set
• proca list-orgs

and so on

[aaronelliotross]

While working on getting proca-api setup and running in our production setup, I ran into a few things I would have liked:

• set the admin password rather than it being random
• set the seed data "org name", i.e. define the organisations for the install
• create widgets / pages / campaigns for the install
• create users

I think the commands you're describing would make all that possible.

[tttp]

@aaronelliotross, one you get the admin/user handle, you can already handle the "normal" creations (widget/page/org) via the api, it's "only" a matter of documentation, right?

IMO the command line as part of the server mostly makes sense for stuff that can't be done via the api (eg. "sudo" type of operations), for the rest, api is your friend and either via proca or proca-cli should work, wouldn't it?

[aaronelliotross]

@Xavier Sorry, I'm not sure what you're suggesting. Can you lay it out in a little more detail? On 2021-09-09 09:33:29, xavier dutoit @.***> wrote: @aaronelliotross [https://github.com/aaronelliotross], one you get the admin/user handle, you can already handle the "normal" creations (widget/page/org) via the api, it's "only" a matter of documentation, right? IMO the command line as part of the server mostly makes sense for stuff that can't be done via the api (eg. "sudo" type of operations), for the rest, api is your friend and either via proca or proca-cli should work, wouldn't it? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub [https://github.com/fixthestatusquo/proca-server/issues/19#issuecomment-915838088], or unsubscribe [https://github.com/notifications/unsubscribe-auth/AAA4RTXIUCBGTXPHIDUEFDDUBBPMNANCNFSM5DSCKRIQ]. Triage notifications on the go with GitHub Mobile for iOS [https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675] or Android [https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub].

[tttp]

Hi really like the idea off the server being headless with mostly api allowing any interface.

most of the "normal" actions you mention (creating an org, creating an action page...) are possible to do via the api. What'd be the benefit of adding them as part of the server cli?

IMO, only stuff that can't be done via the api (eg "setting up the password of the super admin") should be part of the server cli, the rest should be with a normal api (and accessible via proca-cli or whatever poison you prefer as your api wrapper)

does it clarify? I might be completely misunderstanding your aim here ;)

[aaronelliotross]

Ah, yah that makes sense - as long as we can set the admin user / password, then calling the API works fine. On 2021-09-09 20:55:57, xavier dutoit @.***> wrote: Hi really like the idea off the server being headless with mostly api allowing any interface. most of the "normal" actions you mention (creating an org, creating an action page...) are possible to do via the api. What'd be the benefit of adding them as part of the server cli? IMO, only stuff that can't be done via the api (eg "setting up the password of the super admin") should be part of the server cli, the rest should be with a normal api (and accessible via proca-cli or whatever poison you prefer as your api wrapper) does it clarify? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub [https://github.com/fixthestatusquo/proca-server/issues/19#issuecomment-916354528], or unsubscribe [https://github.com/notifications/unsubscribe-auth/AAA4RTU5QUSYBUUABQE5SN3UBD7LXANCNFSM5DSCKRIQ]. Triage notifications on the go with GitHub Mobile for iOS [https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675] or Android [https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub].