So we're using the usual EB domains <<domain>>.<<region>>.elasticbeanstalk.com.
Yet we screwed with the <<domain>> part and we'd like to change it without deleting the environment completely and recreating it.
Still... I don't see how!
Any help?
After a lot of tinkering I found a hacky way to achieve it.
So no... there's no option to change it, but! You can create a new environment with the correct url and later on. In the environment action, swap url.
It literally just swaps them and then you can delete your newly created environment.
Related
I am using vcxsrv to run graphical applications on a linux-cluster. However when I started using it and was asked to select a display setting, I selected one large window and saved this configuration. Now I found that one large window is quite impractical in many cases and would like to change it to multiple windows but don't know how. I am not shown the dialogue-box for choosing the display settings anymore when launching the application and I was looking for some config.xlaunch file that I read about in another post but couldn't find any. I am also not sure where this file would be saved. maybe I was just searching in the wrong place.
Does anybody know how to reset the display settings or where the config file is usually saved?
Simply execute "vcxsrv.exe" from your VcXsrv install directory.
This isn't exactly a question in need of help, however, I am curious as to which file is updated, when updated, when I use Heroku via Github. Would it be the one within my Github or does Heroku save those files and update them somewhere else?
All I'm trying to accomplish is edit a JSON file so I can store an integer to each player (I'm using a worker, for a discord bot). Also, yes, that seems like what I am trying to do. Anything that saves the information, doesn't require money and isn't too complex
EDIT:
This issue has been solved with the answer that Heroku simply cannot update JSON files. I have resolved it myself by moving my host onto a Raspberry Pi 3 Model B+. Thank you for all the answers.
When you use Heroku's GitHub Sync feature, a deployment will retrieve your code directly from GitHub.
Those files aren't saved anywhere else. A new deployment from master will take the code fresh from GitHub.
All I'm trying to accomplish is edit a JSON file so I can store an integer to each player (I'm using a worker, for a discord bot). Also, yes, that seems like what I am trying to do. Anything that saves the information, doesn't require money and isn't too complex
Heroku's filesystem is ephemeral. Any changes you save to the local filesystem will be lost when your dyno restarts, which happens frequently. If you scale your application to multiple dynos you'll also run into trouble since the ephemeral filesystems are dyno-local.
Your best bet is to use a proper client-server datastore, like PostgreSQL. Heroku provides its own Postgres service, which has a free tier. If Postgres isn't to your liking, feel free to choose something else.
My site is a bit more of a static site. The site is based on word-press now, and I am thinking of using auto scale feature.
The problem is that I am not good at startup scripts like python, java, etc...
I am more comfortable with bash script.
Is there a way create a snapshot of a production compute-engine and use it as a template instead of instance group without startup script complexity?
I have two instances, one is an individual instance and one is an inside instance group for auto scale. Whenever there is a update in my site, I have to change it in individual instance and move the snapshot disk as template in instance group and everything will be updated.
My question is, is that workable or do I really have to work on startup script?
Any friendly advice will be highly appreciated.
Some bash skills should be enough to write a startup script and not use the additional instance and image creation at all. See documentation for an easy example of that - just put in all bash commands that you use to prepare that instance yourself. This should be relatively easy and allows for easy modification of that process later on.
If you really want to avoid writing the script, what you’ve described should be possible: take an instance that has everything installed as you like it, then delete it keeping the disk and create an image out of that disk.
One minor improvement: you can use an instance from the existing instance group by abandoning it.
I've done a lot of WordPress migrations from one server to another at work and elsewhere, but one strange thing I've never been able to understand is why widget settings never get carried over.
I'll dump the MySQL database, find/replace localhost with the live domain, SSH the database up to the live server, and then ftp the whole WP installation (core and theme, from my local machine), and still the widget settings are wiped out. And sometimes this is also the case with values saved in theme options pages I make in the Dashboard.
What am I missing?
Wordpress stores widget options - and some plugins and themes also store their options - as serialized data, and so you have to be more careful than a full find/replace of the URLs.
Much more comprehensive answer and some other ways to do move databases and retain serialized data: https://wordpress.stackexchange.com/questions/9076/why-is-my-database-import-losing-text-widget-data
To move a wordpress site and to reconvert all serialized data I used this script.
the using is very simple, download the script, change the credential variable to the database inside the php script and run it.
link to download the script:
http://davidcoveney.com/575/php-serialization-fix-for-wordpress-migrations/
work fine.
Don't do it manually!
Dont edit database manually when migrating between different domains!
Use small scripts, like this:
Wordpress-Migrator.php (read description too.)
because SERIALIZED arrays needs to be modified specifically too!!!
After having seriously database loosing problems, I decided to go for an autobackup system. I researched and AutoMySQLBackup looks fine.
I use Bluehost, where should I locate the automysqlbackup.sh file? I just worry about security issue. Also, where should we locate the backup files?
Appreciate! thanks a lot!
I don't know bluehost, but definitely put it outside the web root if you can. If you can't, create a new directory, put the shell script and a .htaccess file saying
Deny from all
in it. That should block it for access from outside with a 403 error - make sure you test.
Putting it outside the web root is the way better option IMO, especially if it contains sensitive data.