More deployment options

[patrickbeeson]

More deployment options

[krallin]

Hey there,

In Cactus v3, we support S3, Rackspace Cloud Files (which could probably support Swift in general pretty easily), and Google Cloud Storage.

Did you have something else in mind?

Cheers,

[patrickbeeson]

Cool, didn't realize that. I'd love to be able to deploy to WebFaction.

[krallin]

The interface in v3 is supposed to be pluggable, so you be able to add this
as a deployment option.

Let me know how it goes / if you need help getting familiar with the
architecture.

Cheers,

[patrickbeeson]

Great. I'll take a look. Thanks!

[adamwintle]

+1 for Github pages

[stefanooldeman]

dibs on Github pages. I'll be gladly looking into this and propose a pull request.

[w4nderlust]

What do you think about ading a simple ftp deployment? With just host, username, password and destination directory

[krallin]

@w4nderlust ,

This should be rather easy to write as a deployment engine. If you're interested in working on this, just let me know, and I'll provide some tips to get you started.

Cheers,

[w4nderlust]

Yes, give me some pointers and I'll try :)

[krallin]

@w4nderlust,

Basically, there are three things you need. I suggest you use the Rackspace examples here, they're probably the simplest:

https://github.com/koenbok/Cactus/blob/master/cactus/deployment/cloudfiles/

You need to:

Create a credentials manager. This basically is just an object that tells Cactus where and how to store Credentials. This is really trivial, yours should probably look like this:

class FTPCredentialsManager(BaseKeyringCredentialsManager):
    _username_config_entry = "ftp-username"
    _password_display_name = "FTP Password"
    _keyring_service = "cactus/ftp"

Next, create the deployment engine. This class should take care of all preparation work in the configure() method. In your case, this may be... nothing.

This should inherit from the BaseEngine defined here: https://github.com/koenbok/Cactus/blob/master/cactus/deployment/engine.py

The actual entrypoint called by Cactus is deploy(). This calls into the last thing you need to create, which is the file class. The file class is basically a class that should know how to deploy a given file. It should inherit from BaseFile.

There, you'll want to define do_upload and remote_changed (though the former can just return True unconditionally, but that wouldn't be ideal). Like the name implies, do_upload should upload your file.

You can pull in additional dependencies if needed. Just make sure you make them optional (look at the existing setup.py).

Let me know if you need further help,

Cheers,

@w4nderlust are you still working on a ftp deployment engine?

[w4nderlust]

I haven't started yet actually, I was thinking of doing it this week.

Il giorno 17/mag/2015, alle ore 21:27, pani-c [email protected] ha scritto:

@w4nderlust https://github.com/w4nderlust are you still working on a ftp deployment engine?

—
Reply to this email directly or view it on GitHub #80 (comment).

Please leave a note if you're up to something ;-)

[facconi]

Hi everybody! Any news about a standard FTP deployment engine?

I was looking into pysftp but had trouble with its dependencies :(

[syllog1sm]

@krallin like this? syllog1sm@6e458b5

Doesn't complete any of the actual work yet. But the skeleton should be right, right?

Edit: It looks like there also needs to be CLI hooks for the deployment options? I can't figure out the entry point to these.

[dwightgunning]

For a straight local file system deployment, I have raise PR #171.

[Ollie-w]

How about Netlify? How would I deploy using that?