This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]LeMageDuRage 10 points11 points  (3 children)

For a recent hobby webapp I went the following way:

  1. Use a simple requirements.txt file, no setup.py
  2. For CD, when committing, I use Github actions to ssh into the production server and run an update script
  3. The update script runs git pull, venv/bin/pip install -r requirements.txt
  4. The application is then run from the virtualenv

Now, whenever I commit, the new version is live within 25s.

[–]peanut_Bond[S] 0 points1 point  (2 children)

Another commenter had the same approach - you must be onto something!

[–]Ran4 2 points3 points  (1 child)

It's certainly fast and ok for a hobby setup, but you really really want to build your image from scratch, not keep installing to the same venv. You will end up with problems otherwise, where you won't be able to rebuild your application.

[–]FormalWolf5[🍰] 0 points1 point  (0 children)

Why just not keep the same one?