Open Coiot opened 1 year ago
Hey! Have you checked out this guide?
We use the exact same deployment setup for the editable.website template.
https://www.postowl.com/docs/administration-guide/deploy/
Please have a look and let me know if it worked for you. Will also test and update the README here, just a bit short on time atm.
PS: We are working on making deployments super easy, so even non technical people can deploy and update an "editable website".
My work-around solution was to run build locally and remove the build step from the Docker file and /build from dockerignore. Without doing so, every fly deploy after the initial one would not build.
Loving the setup, tho. Have an in-progress site at https://nwahlc.fly.dev
start deploy with this command
fly deploy \
--build-secret DB_PATH="./data/db.sqlite3" \
--build-secret ADMIN_PASSWORD="1234" \
--build-secret ORIGIN="https://denemedeploy1234.fly.dev"
https://denemedeploy1234.fly.dev/login and go url but icant login with 1234
Followed the instructions step by step but never got it running, all I get is uh... nothing. The fly monitoring shows infinite restarts of the machine.
After running fly deploy as shown in the readme.md everything looks fine in the terminal except this near the end :
WARNING The app is not listening on the expected address and will not be reachable by fly-proxy.71f5d7e68 [app] update finished: success You can fix this by configuring your app to listen on the following addresses:
- 0.0.0.0:3000 Found these processes inside the machine with open listening sockets: PROCESS | ADDRESSES -----------------*--------------------------------------- /.fly/hallpass | [fdaa:6:8426:a7b:169:7e71:c9af:2]:22
Does this means something to anybody ? Thank you
Weird error. Mhh, can you try deploy the postowl app, instead of editable.website?
https://www.postowl.com/docs/administration-guide/deploy/
It's possible that I missed migrating some changes to README.
Let me know if deploying postowl worked for you.
Currently when deploying this template to Fly.io it will deploy well the first time, but then any further fly deploy command to make an update results in a 500 Internal Error, even if there has been no code change.