search

ogallagher / tejos_textiles

An online arts journal for publishing works in a new medium
MIT License
1 stars 0 forks source link

Migrate from heroku #42

Closed ogallagher closed 4 years ago

ogallagher commented 4 years ago

Some other that the hosted webserver, there were some other resources provisioned through heroku (as in the database and memcache dictionary) which will need to be migrated.

The MySQL database (provided by JawsDB in heroku) actually is hosted by aws, so I’ll just be skipping the middleman in that case.

The memcache server may be a bit less clear to set up (provided by Redis Labs in heroku), but I think aws Elasticache for Memcached should do the trick.

I also can get rid of documentation and source code related to the heroku environment.

ogallagher commented 4 years ago

The database migration appears to be working, at least in my local test environment. What stumped me for a while was that the default security group for the database had a source restriction for inbound connections, which I removed. The memcache server is a bit more confusing because I’m having a hard time finding the needed credentials (user, pass) to set up the connection.

ogallagher commented 4 years ago

I’m moving forward still with the memcache server, though an issue I’ve discovered is that aws does not allow them to be accessed outside of their vpc, so I can’t test the memcache server in my local test environment (my laptop).

ogallagher commented 4 years ago

The connection from the EC2 webserver instance to the memcached instance now works. Given the new database and new memcache, this issue is resolved.