dimaslz/dimaslz Deploy

Automate deploying websites in server with docker

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
server_ipIP of your machine to deploy the applications, example: 12.34.56.78yes
userUser to connect to your machine, example: rootyes
ssh_private_keySSH private key from your application secrets, to connect to the server, example: "secrets.CONNECTION_PRIVATE_KEY"yes
app_hostapplication host, as for example: your-domain.com. Will create a config to serve the application in: `${app_name}.your-domain.com`yes
app_nameapplication name in kebab case format, as for example: my-app. Finally will serve the application in: https://my-app.your-domain.com. By default repo nameno
app_portsport where is serve the application, for example: 8080no
sourcewhere the application create the build. By default /distno
dockerfiledo you want to deploy an specific Dockerfile?. Setup the source as for example: '.'no
envyour environment vars for the app. Check demo in README.mdno
staticboolean, by default false. Will create the environment for an static o server appno
run_commandfor static sites, will is not needed command, for server apps, by default will use `yarn start`, but you can specify the command to run your application for any stackno
build_commandby default, we will use 'yarn build' but, you can specify an specific commandno
wildcard_sslby default 'false', set to 'true' if the final url of the project is *.*.domain.tld and, automatically, the action will create an SSL certificate by Certbot (not ready to use, experimental WIP)no
env_nameby default 'production', but you can setup the tag as you want. This will not affect to the domain.no
repo_tokenby default null, but you can setup repo_token: 'secrets.GITHUB_TOKEN'no

no outputs