New Module Puts All Path/URL Config On One Page

The blog post said I was unauthorized so here is what I wrote -

Here’s one for you -

How about a method of just entering a domain (http://www.site.com) and Deeploy just prepends all URL fields with this so http://local.site.com/themes becomes http://www.site.com/themes etc and the same for the server path fields?

Obviously this wouldn’t be helpful for MSM sites but for single sites this would eliminate copy/paste errors and a whole lot of tedium for large sites with a lot of upload file preferences and weblogs.

How’s that FieldFrame field coming along too? 😉

A big second on everything that StinHambo had to say in the post above mine.

I’m getting when changing to a different site via MSM (in the CP).

Warning: Invalid argument supplied for foreach() in /www/eh0000/public_html/admin/modules/deeploy_helper/mcp.deeploy_helper.php on line 323

Thanks Steven – I’ll check it out.

Justin

Hi Justin,

It seems to kick in if I change sites while in the Deeploy Helper screen. Not a show stopper so don’t panic!

PS. If I can add a couple of suggestions -

• Replace Field (master fields for URL and Server Path and tick boxes for replace)
• Fieldframe option

Hey Steven, just wanted to follow up – these are both on the roadmap, and the FieldFrame bit is halfway coded. I can’t say when it’ll be out, but we definitely haven’t forgotten.

Thanks! Justin

IMHO, it’s incredible that this needs to be a module at all …

anyway, great work Hoosteeno! 😊

But how does this work for a live site? If you move a site from develop to production, you won’t even be allowed to login to the backend without changing the config.

• bjorn

Like Bjorn, I’d be interested in seeing how people are using this in practice. What are the steps you’d take when moving a site on a local dev server to a live server?

I like to have a config.php file with server variables that get automatically written to. This cuts out a bit of work and means the CP is styled correctly immediately.

Like Bjorn, I’d be interested in seeing how people are using this in practice. What are the steps you’d take when moving a site on a local dev server to a live server?

I login to an unstyled CP and then go to this module and change everything in one step. voila CP is styled and everything works the way it should.

Great work, no more clicking around for ages in the control panel!

I would like to add my support for the stinhambo’s suggestion for a field where I can insert the URL once and it gets prepended to the fields..

I have a few sites that uses the gallery module - support for the gallery preferences would be great..

Delpoy Helper is a great module. Have been using it for many months on a MSM enabled site without issue.

I normally take a db dump from my live server to install on my local install every 3 or 4 weeks and sync the files from live to dev install. Deploy Helper reduces my setup on the local dev server from 90 minutes to around 20 minutes. This could further be improved if the Gallery Module was also supported (Hint Hint 😊 )

Hello all, and thank you for the feature requests, bug reports, and discussion!

I’m here to announce Deeploy Helper 1.1.0, which includes several of your most requested features…

• Support for FieldFrame (1.1.3 and above).
• Support for Gallery.
• A super cool quick replace tool at the top.

I hope you like this new release.

As always, the standard disclaimer applies: Deeploy Helper should be used with great caution on well-backed-up systems. It works on some of the most critical tables in your database; a bug, a conflict with another module, or a misplaced keystroke could hose your install.

Special thanks to Steven Hambo for testing!

Justin

Hello Justin,

Some posters in this thread were curious about how Deploy Helper is being used in production. I’d like to describe the scenario I’m facing and ask you (or others) if Deploy Helper would be applicable. If so, I’m sure others would find this helpful as it has to do syncing databases.

I’m moving a live site from one server (“Server 1”) to another server (“Server 2”). So it’s not the typical “dev to production” migration, it’s more like a “production server to production server” migration.

Obviously only one of those servers will be live at one time. Currently “Server 1” is live although all the files and db are migrated to “Server 2” and all the paths adjusted.

While I test “Server 2” for the next day or two “Server 1” is still live, still enrolling new members, still adding new posts and comments and so on. When it’s time for “Server 2” to go live, it’s db will be slightly outdated. Instead of attempting some fancy db sync my plan is to just migrate the db over again (from Server 1 to Server 2). This is where I’m hoping Deploy Helper might come in handy.

The current live site “Server 1” does not have Deploy Helper installed. If I install Deploy Helper on “Server 2” and them copy over the db from “Server 1” (which does not have Deploy Helper), what do you see happening?

I suppose it’s entirely possible that Deploy Helper relies on the db and so my action will break Deploy Helper on Server 2. But if not, than I’d be able to “sync” the two db’s without worrying about having to change the paths and such - thereby greatly easing the migration.

Many thanks! vik