HOWTO migrate stuff automatically from WebFaction!

sean

cworrell I just noticed that the wf_generic_php migration sets up our app as php-fpm+nginx instead of php+apache as before.

We can flip the app type for you from our end if you need us to.

cworrell Would it be possible to add another parameter too for the app name on opalstack's side?

Logged that feature request earlier today.

cworrell

sean We can flip the app type for you from our end if you need us to.

that's great, but not super helpful when I'm working on migrating a site and have to wait several hours for support to change it for me. I know response times are higher during all the migrations and you guys are doing awesome, but being able to change it myself or do this workaround allows me to move on to our next site migration quicker.

bones10

I'm trying to migrate a wordpress site. The simulation gave me one warning. I told it to go, but I got an error, looks like on creating the database. I possibly could have incorrect values in my config.ini file.

What should I have for php_version? the version on my webfaction site's php version?
I'm not sure what to put for fpm_max_children or fpm_max_requests.

And I left the entire [local_db] section untouched. It seemed like it it might be right.

Am I supposed to create a database on the opal stack side first?

Thanks for the help.

sean

bones10

if you're running a reasonably recent version of Wordpress then the following should be OK:

[php]
php_version = 74
fpm_max_children = 5
fpm_max_requests = 20

[local_db]
db_host = localhost
db_port = 3306
db_user = 
db_name = 
db_pass =

snaushads

sean I am getting an error when running the simulation. Changed password to keep them simple as well. Able to login to WF panel and ssh with those passwords.

Error
Traceback (most recent call last): File "/usr/local/bin/wfmigrate", line 70, in <module> migrator = __import__(COMPONENTS[args.component]['module']).Migrator(cfg, args) File "/opt/app_migrators-1.6.0/wf_wordpress/migrator.py", line 27, in __init__ self.wf_cfg = WfCfg(cfg['webfaction']) File "/opt/app_migrators-1.6.0/lib/config_types/wf_cfg.py", line 12, in __init__ self.update_derived_attrs() File "/opt/app_migrators-1.6.0/lib/config_types/wf_cfg.py", line 16, in update_derived_attrs self.wf_session_id, self.wf_account_cfg = self.wf_api.login(self.wf_account, self.wf_password, self.wf_server.capitalize(), 2) File "/usr/lib64/python3.6/xmlrpc/client.py", line 1112, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python3.6/xmlrpc/client.py", line 1452, in __request verbose=self.__verbose File "/usr/lib64/python3.6/xmlrpc/client.py", line 1154, in request return self.single_request(host, handler, request_body, verbose) File "/usr/lib64/python3.6/xmlrpc/client.py", line 1170, in single_request return self.parse_response(resp) File "/usr/lib64/python3.6/xmlrpc/client.py", line 1342, in parse_response return u.close() File "/usr/lib64/python3.6/xmlrpc/client.py", line 656, in close raise Fault(**self._stack[0]) xmlrpc.client.Fault: <Fault 1: 'Not allowed to login to machine "Web461"'>

sean

snaushads WebFaction does not have a web461 server:

$ host web461.webfaction.com
Host web461.webfaction.com not found: 3(NXDOMAIN)

I think maybe you meant to use web641 instead?

bones10

I got my site migrated. Now I'm trying to test it with my account domain. My site is/was https with an ssl certificate.

When I try to test (loginname.opalstacked.com/wp-admin) it redirects to an https path and says "404 Not Found"

I've turned on "shared certificate" in the "Site Routes" page. note this is just for testing. I'll add my certificate later when I'm ready to deploy the site.

Thanks for the help.

bones10

never mind - I just didn't wait long enough. Sorry to bother.

sean

bones10 no bother at all 🙂

sean

cworrell point taken! 🙂 I'll get the ball rolling on that and will let you know when it is ready.

bones10

I've set MX records for my site to send email to Google Workspaces. I'm still using site.username.opalstackd.com to test it out. Is there away to see if the email is working before I go live? And do I need to create email addresses in opalstack too? It's been a while since i've had to mess with these type of settings.

sean

bones10 If you're using Google Workspace for your mail then you don't need to add your addresses here.

I don't think you'll be able to test delivery for your domain's Google MX records on our end before you cut your NS over, but if you want to check for the presence of the records themselves then you can run this as one of your shell users (or as any user on a machine that has dig installed):

for ns in ns{1..3}.us.opalstack.com; do
  echo $ns;
  dig +short NS domain.com
done

Change the us to de or sg if you're using the other regional NS.

psddp

Can it migrate PHP (symfony) symlink apps?

sean

psddp no, sorry. symlink apps can't be migrated at this time.

psddp

@sean Alrigth, symlink apps are easy to recreate manually.
Beside that, I just used the migrator for emails and it works like a charm! 😃

wherry

After we have migrated a WF PostgreSQL db to your service, what is the hostname for the db if you are trying to connect an external django app (outside of opalstack) to the opalstack database?

'default': {
'ENGINE': 'django.db.backends.postgresql_psycopg2', # Add 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 'oracle'.
'NAME': '<my opalstack db name>', # Or path to database file if using sqlite3.
'USER': '<my opalstack db user name>', # Not used with sqlite3.
'PASSWORD': 'xxxx', # Not used with sqlite3.
'HOST': '<what goes here???>', # Set to empty string for localhost. Not used with sqlite3.
'PORT': '5432', # Set to empty string for default. Not used with sqlite3.
}

sean

wherry If you want to connect to our managed PostgreSQL remotely then you'll need to do so through a SSH tunnel.

tcw

This tool is really excellent - have successfully migrated a number of wordpress sites. Thank you!

Can this tool be used to migrate static sites easily? e.g. Does the generic PHP apply, and can the application type be changed later?

(Obviously direct copy is easier than for wordpress-sites, but direct migration would be amazing!)

sean

tcw and all: we rolled out some changes last night that include options for migrating static and symliink apps:

# wfmigrate --help
usage: wfmigrate [-h]
                 {domains,maria,psql,email,email-data,php,php-symlink,port,staticonly,staticonly-symlink,wordpress}
                 ...

WF -> Opalstack Migrator

positional arguments:
  {domains,maria,psql,email,email-data,php,php-symlink,port,staticonly,staticonly-symlink,wordpress}
                        Migration Component
    domains             Domains
    maria               MariaDB (for MySQL databases)
    psql                PostgreSQL (for PostgreSQL databases)
    email               Email
    email-data          Email Data (Import & Deduplication)
    php                 Generic PHP
    php-symlink         Generic Symlink to PHP
    port                Generic Proxy-Port (custom app listening on port)
    staticonly          Generic Static-Only (no .htaccess)
    staticonly-symlink  Generic Symlink to Static-Only (no .htaccess)
    wordpress           Wordpress

optional arguments:
  -h, --help            show this help message and exit

There's also an email-data migrator there which will copy your mailbox contents into your existing mailboxes here at Opalstack, eg you do the email migrator to make the addresses and mailboxes then the email-data migrator to copy everything over. The email data migrator works best if you're starting with an empty Opalstack mailbox but it should work if you've already copied stuff over.

All of these new migration features work like the other features: copy the config template, edit to put in your info, simulate, and run.

Hoping to have all of the new features more-fully documented this weekend.

kurt

sean Thanks for adding all of the new migrators. I will be trying a number of the new ones out.

Unfortunately, domain, the first I tried, is not working yet for me.

At the beginning of the logs, I see a ton of DEBUG lines and 200 status codes - no warnings, errors or anything that looks problematic.

Then I see:

DEBUG : performing POST domain/add/ with [JSON array with ~153 domain name objects]
DEBUG : Starting new HTTPS connection (1): my.opalstack.com:443
DEBUG : https://my.opalstack.com:443 "POST /api/v0/domain/add/ HTTP/1.1" 400 553
DEBUG : [array with ~150 empty objects, interspersed by 3 of this object: {"name":["Invalid domain name."]}]

I'm reasonably sure all of my wf domain names are valid, so it's unclear what's up here.

« Previous Page Next Page »