https://blog.pgxn.org/tags/skeleton/Skeleton2011-05-23T04:53:30ZThe PGXN MaintainersHugohttps://blog.pgxn.org/post/5758832725PGXN Utils 0.1.1 Released!2026-10-07T16:13:48Z2011-05-23T04:53:30ZDickson S. GuedesHello everyone!

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.

]]>Hello everyone!

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! “:)

]]>https://blog.pgxn.org/post/5465631144PGXN Utils2026-10-07T16:13:48Z2011-05-14T01:05:00ZDickson S. GuedesDo you ever have problems with copy and paste? I often did, and that is why I create custom templates for often used files that match certain patterns.

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.

]]>Do you ever have problems with copy and paste? I often did, and that is why I create custom templates for often used files that match certain patterns.

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?

  1. First install it:

    gem install pgxn_utils

  2. 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!

]]>