I’m proud to tell you that a new version of pgxn_utils was released!
Now you can release a distribution to PGXN in five steps!
First, install it:
gem install pgxn_utils
Second, create your extension, optionally overwrite some defaults:
mkdir $HOME/extensions
cd $HOME/extensions
pgxn_utils skeleton my_extension --maintainer "Dickson S. Guedes"
Third, code!
Fourth, bundle it:
pgxn_utils bundle my_extension
Extension generated at: /home/guedes/extensions/my_extension-0.0.1.zip
Fifth, release it:
pgxn_utils release my_extension-0.0.1.zip
Enter your PGXN username: guedes
Enter your PGXN password: ******
Trying to release my_cool_extension-0.0.1.zip ... released successfully!
Visit: https://manager.pgxn.org/distributions/my_cool_extension/0.0.1
Ah, you can export PGXN_USER and PGXN_PASSWORD if you are tired to type
your username and password every time.
I’m proud to tell you that a new version of pgxn_utils was released!
Now you can release a distribution to PGXN in five steps!
First, install it:
gem install pgxn_utils
Second, create your extension, optionally overwrite some defaults:
mkdir $HOME/extensions
cd $HOME/extensions
pgxn_utils skeleton my_extension --maintainer "Dickson S. Guedes"
Third, code!
Fourth, bundle it:
pgxn_utils bundle my_extension
Extension generated at: /home/guedes/extensions/my_extension-0.0.1.zip
Fifth, release it:
pgxn_utils release my_extension-0.0.1.zip
Enter your PGXN username: guedes
Enter your PGXN password: ******
Trying to release my_cool_extension-0.0.1.zip ... released successfully!
Visit: https://manager.pgxn.org/distributions/my_cool_extension/0.0.1
Ah, you can export PGXN_USER and PGXN_PASSWORD if you are tired to type
your username and password every time.
This was a productive weekend that allowed me to work on some new features in pgxn_utils and I’m proud to tell you that a new version was released!
Trying to simplify your extension-development life I’ve added two tasks to
pgxn_utils: change and bundle. The first one is just a convenient way to
change META information about extension, incrementally, the second one is an
easy way to archive your extension in a zip file well named.
This was a productive weekend that allowed me to work on some new features in pgxn_utils and I’m proud to tell you that a new version was released!
Trying to simplify your extension-development life I’ve added two tasks to
pgxn_utils: change and bundle. The first one is just a convenient way to
change META information about extension, incrementally, the second one is an
easy way to archive your extension in a zip file well named.
To install it just type:
gem install pgxn_utils
Or, if you don’t want to install it yet, see it in action on this screencast 3:05.
Work in progress…
I’m working now to simplify the release, creating a task to send bundled file to PGXN.
There are a lot of work to do yet so, please, tell me if you found a bug or have suggestions.
Have a nice code! “:)
]]>With files from the structure of PostgreSQL’s extensions was the same thing.
I was tired of creating the files and edit the META, controlfile, READMEs, etc. every time I start a new extension and felt that I need something that made me more productive, so I decided to create an automatic generator and share it with the world.
]]>With files from the structure of PostgreSQL’s extensions was the same thing.
I was tired of creating the files and edit the META, controlfile, READMEs, etc. every time I start a new extension and felt that I need something that made me more productive, so I decided to create an automatic generator and share it with the world.
I called it pgxn-utils, and you should give it a try: it is easy to install, easy to use and will help you to start hacking quickly!
How?
First install it:
gem install pgxn_utils
Then start a new extension:
pgxn_utils skeleton my_cool_extension
Thats all! It will create the initial skeleton for you and you can start coding! But, if you don’t want to install it, see it in action
Good hack!
]]>