Replies: 2 comments
|
The best way to handle this now is to have separate environments with your host, like on Railway, you can have multiple environments like dev/staging and production. I plan to add sandboxes and environments directly to Instatic, so it could be handled from the same install eventually, like branches on Github, you could just create a new environment, and pull / push between them. What do you think? |
0 replies
|
Yes...if it could be pulled/pushed into github that would be fantastic. One repository per website. This would make the site immutable even if there was a successful attack on the host. I'm curious with Railway. Can you have multiple websites on a single instance of Railway? I've never heard of them till I saw your project. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I would like see something like this for those websites that are edited by a client or someone other than yourself.
Flowchart:
Development/build copy
↓
Production site
↑
client edits production
↓
How does development know
about those edits?
All reactions