Support/Comments for PackMan 1.1.0-pl

This is an auto-generated topic for PackMan 1.1.0-pl by splittingred.

Brief Description:

PackMan is a Transport Package building tool for packing up Templates, TVs, Snippets, Chunks and other Packages into a Transport Package, ready for distribution.
New in 1.1.0

• Added French, German translations
• Fixed authorization check bug
• Added ability to save package setup into "Profiles" for easy reloading
• Added ability to package in Plugins, automatically adds Plugin Events
• Added ability to package in stand-alone directories for file transfers

See official documentation here:http://svn.modxcms.com/docs/display/ADDON/PackMan

I know this is a generic problem, but it’s only happened today having used Packman to deploy a directory from dev Revo to a staging Revo (on a shared host). The directory on the target machine has been created by the nobody user, and I can’t seem to chown my way out of it. It’s my images folder under assets, and it won’t let me change permissions to add more files. (It won’t let me do anything actually, I can’t even remove it).

Is there any way I can solve this? Or do I have to uninstall my package and then re-create it without that directory (assuming that it deletes the directory on uninstall)?

So all files copied on the new server are done as nobody? Sounds like you need to make PHP run as a user in a group on that server that you can also edit files with.

If you want to remove it, try deleting the directory from the files tree in Revo.

Thanks.

Unfortunately my hosting setup won’t let me run as another user. What I did in the end is remove the package, manually create the directories, and then reinstall. That probably means those particular files are baked into the directory now, but it’s a working compromise and I can at least add new files.

By the way, between removing the package and reinstalling it I added a system key ’new_folder_permissions’ set to 0777 (copied from another install). It didn’t appear to work - I’ve also tried installing the same package into this new install and folder permissions are still set to 0755.

And secondly, when trying to update the key’s name in the ’nobody’ install (I’d literally copied ’setting_new_folder_permissions’ from the other install) it won’t update it.

Not sure if these are bugs, or the whole permissions area is so environment dependent that it’s not possible to nail down.

Permissions are very much environment-dependent. Some allow the chmod() function, others do not. Some require certain permissions (typically CGI/FastCGI environments require 755 for directories and 644 for files). Windows servers are a different matter altogether.

This may be a daft/simple question, but I can’t find the answer anywhere:

I’ve created a package using packman - all good so far

How do I deploy this on another MODx site?

- Upload the zip to the core/packages/ directory.
- Go to Package Management in the MODX install you want to install it to.
- Click the ’Add New Package’ button.
- Check the 3rd option, "Search Locally for Packages" and hit OK.
- Click OK.
- Install your package.
- Go have a beer.

Thank you!!!