An enterprise client's firewall inexplicably started blocking our third-party video CDN and some third-party domains running endpoints and hosting scripts we needed for our web app.

With Joseph @ Elestio's help, I spun up a load balancer, and configured it to proxy three domains over to the original servers, with SSL termination, etc.

Now proxying those requests through our domains, our service is back up (while we're still waiting for the client's IT group to unblock those CDN's...)

Unbelievable service and I'm so grateful to have something so powerful at my fingertips.

Recently, we had to ensure our cloud services had a local backup for compliance reasons.

I wrote a script for our local server to connect to our Elestio instance via ssh, and extract files and database info from the app.

Notes:

1. The database extraction only applies if you're using a database
2. Your app's specific files are likely mapped to the /opt/app/app_name folder on your local instance, which is what I back up. IF THEY ARE NOT MAPPED, I.E. ONLY IN A DOCKER VOLUME, THIS WILL NOT BACK THEM UP.
3. This will back up sensitive info, like your .env file which could include passwords, API keys, etc. Ensure your backups are properly secured.
4. If you don't already have it in place, you'll need to create an SSH keypair on the computer this will run on, and install it locally and on your Elest.io server.

Caveats aside, I'm sharing this here in case it's helpful to anyone. You'll likely need to modify it a bit for your environment.

app=your-app-name-here
today=$(date "+%Y-%m-%-d")
base="/path/to/root/folder/of/backups"
backupFolder="$app/$today"
filepath="$base/$backupFolder"
mkdir "$filepath"
echo "Root path for backup operations: $base"
echo "Backing up to folder: $backupFolder"
echo "-------------============= Export operations begin ============--------------"

db_container=name_of_mysql_docker_container
db_user=database_username_here
db_password=database_password_here
db=database_to_backup

echo "Backing up $app to $filepath"

# backing up database from container
ssh -T root@your-elestio-url "docker exec $db_container /usr/bin/mysqldump -u $db_user -p$db_password --single-transaction $db" > "$filepath/$app_db-$today.backup.sql"

# back up data present in app folder
ssh -T root@your-elestio-url "tar -czvf - -C /opt/app/$app ." > "$filepath/$app_files-$today.backup.tar.gz"


echo "-------------============= Export operations finished ============--------------"

Thank you!!

Recently, we had to ensure our cloud services had a local backup for compliance reasons.

I wrote a script for our local server to connect to our Elestio instance via ssh, and extract files and database info from the app.

Notes:

1. The database extraction only applies if you're using a database
2. Your app's specific files are likely mapped to the /opt/app/app_name folder on your local instance, which is what I back up. IF THEY ARE NOT MAPPED, I.E. ONLY IN A DOCKER VOLUME, THIS WILL NOT BACK THEM UP.
3. This will back up sensitive info, like your .env file which could include passwords, API keys, etc. Ensure your backups are properly secured.
4. If you don't already have it in place, you'll need to create an SSH keypair on the computer this will run on, and install it locally and on your Elest.io server.

Caveats aside, I'm sharing this here in case it's helpful to anyone. You'll likely need to modify it a bit for your environment.

app=your-app-name-here
today=$(date "+%Y-%m-%-d")
base="/path/to/root/folder/of/backups"
backupFolder="$app/$today"
filepath="$base/$backupFolder"
mkdir "$filepath"
echo "Root path for backup operations: $base"
echo "Backing up to folder: $backupFolder"
echo "-------------============= Export operations begin ============--------------"

db_container=name_of_mysql_docker_container
db_user=database_username_here
db_password=database_password_here
db=database_to_backup

echo "Backing up $app to $filepath"

# backing up database from container
ssh -T root@your-elestio-url "docker exec $db_container /usr/bin/mysqldump -u $db_user -p$db_password --single-transaction $db" > "$filepath/$app_db-$today.backup.sql"

# back up data present in app folder
ssh -T root@your-elestio-url "tar -czvf - -C /opt/app/$app ." > "$filepath/$app_files-$today.backup.tar.gz"


echo "-------------============= Export operations finished ============--------------"

Just wanted to share this excellent product, and perhaps it would be helpful to offer it:

https://www.getlago.com/

Hello, often I am fixing something that requires an update to the ENV vars and also the code.

Whenever this happens, I need to go through two complete builds before I can test the feature in prod... and if I accidentally push the commit before I update the variables in the dashboard... it's 3 builds

Is there a way to cancel in-progress builds ?

This is a tool I’ve been considering recently for our dashboard and reporting.

Would love to deploy on Elest.io- Render and Heroku are already supported

https://github.com/chartbrew/chartbrew

Hello, we have a server here at the office, and we would like to allow one of our Elest.io instances to SSH to the server securely.

I'm thinking the Global Private IP / Nebula system you have in place is the best way to do it, but I don't know how to install / configure a 3rd party computer/server to connect to your automatically-provisioned one.

Any tips welcome!

@jbenguira any ideas?

@VISIGO for example something like this seems like maybe what I need?
https://github.com/serverless-stack/sst

I'm really excited about trying your CI/CD pipeline. We're currently hosting on Netlify, and while their app is awesome, we have some GDPR requirements that are pushing us towards self-hosting.

I've read the documentation but I can't seem to get my app to build (yet :).

Some questions I have:

1. We use a Jamstack tech stack with Microservices backend. Does our repo/app need to have its own server configuration for hosting the HTML/CSS/JS files? (i.e. once the site is 'built', do we have to run the command to host it?)
2. Any suggestions for what framework/server tech to use for deploying functions, ideally something that is lambda-compatible? We have 150+ functions, so rewriting syntax / etc. is not ideal

Something else I'm aware of if I want to really 'replicate' the Netlify experience is that I'll need to figure out how to implement a CDN + cache invalidation hooks, etc... and eventually move edge functions to CF workers or something like that.

Thanks in advance!

An enterprise client's firewall inexplicably started blocking our third-party video CDN and some third-party domains running endpoints and hosting scripts we needed for our web app.

With Joseph @ Elestio's help, I spun up a load balancer, and configured it to proxy three domains over to the original servers, with SSL termination, etc.

Now proxying those requests through our domains, our service is back up (while we're still waiting for the client's IT group to unblock those CDN's...)

Unbelievable service and I'm so grateful to have something so powerful at my fingertips.