Build Digitalocean image automatically upon release #5682
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…an does The scripts run/installed on the server are based on what was given to me by Digitalocean in 2019, so they may have diverged a bit since.
While these don't (yet?) get submitted to the Digitalocean marketplace, it should bring us most of the way of making that possible. The next step would be to somehow get notifications of the new image snapshot sent... Somewhere and have the lovely DO folks test/release it for us.
Without this, it fails when initializing the builder.
This will allow anyone to use the resulting image, and not just those with at least 2GB of ram.
NYC1 is the only DC where the smallest size droplet is available.
- standardize text with the sample marketplace app - remove reference to web server (its unavailable in newer versions)
- use nginx ful rules - limit ssh by default - force enable ufw - drop access to 2375 and 2376 (this allows passwordless docker access...)
This is confusing for users and shouldn't really ever exist.
…ng to their droplet ip/vhost
We'll only ever test against the latest LTS.
josegonzalez
force-pushed
the
build-digitalocean-image
branch
from
61957d7
to
f1152cd
Compare
This should fix a few of the warnings/errors shown during the image check process.
Logs are already zero'd out
github-actions bot
pushed a commit
that referenced
this pull request
Feb 21, 2023
# History ## 0.30.1 Install/update via the bootstrap script: ```shell wget https://dokku.com/install/v0.30.1/bootstrap.sh sudo DOKKU_TAG=v0.30.1 bash bootstrap.sh ``` ### Bug Fixes - #5690: @josegonzalez Update dependencies for golang code to fix builds - #5683: @josegonzalez Ensure the services directory also exists - #5688: @josegonzalez Set custom entrypoint for pack-based containers so custom command/argument combinations are respected ### New Features - #5682: @josegonzalez Build Digitalocean image automatically upon release - #5675: @josegonzalez Add new sections to release notes ### Documentation - #5695: @josegonzalez Add a note about required upgrade to 0.29.x for versions prior to 0.25.x - #5689: @josegonzalez Add note about ubuntu 18.04 being deprecated - #5684: @josegonzalez Note that the app.json is pulled from the specified image when deploying via git:from-image - #5679: @josegonzalez Revert invalid replacement in homepage html path objects - #5678: @josegonzalez Cleanup docs on homepage for installation ### Dependencies - #5693: @dependabot[bot] chore(deps): bump mkdocs-material from 9.0.12 to 9.0.13 in /docs/_build - #5694: @dependabot[bot] chore(deps): bump zipp from 3.13.0 to 3.14.0 in /docs/_build - #5677: @dependabot[bot] chore(deps): bump flask from 2.2.2 to 2.2.3 in /tests/apps/multi - #5676: @dependabot[bot] chore(deps): bump flask from 2.2.2 to 2.2.3 in /tests/apps/python-flask
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is based on the scripts handed to me in 2019, so are likely wildly out of date with their existing release process.
While these don't (yet?) get submitted to the Digitalocean marketplace, it should bring us most of the way of making that possible.
The next step would be to somehow get notifications of the new image snapshot sent... Somewhere and have the lovely DO folks test/release it for us.