You currently have 3 ways of creating an EOS account:

1. Asking an existing user to create an account for you
2. Use an exchange to send a recommended 2-3 EOS to signupeoseos smart-contract/dApp. In the transaction memo you must include  your desired account name followed by a dash and then your desired EOS public key.
3. Use an an account generator service

Since i’m a new user and i wouldn’t want to make crypto payments in the process, i opted for option 3. Most of the services require the payment in crypto.

I found this one: https://create-eos-account-for.me/

It accepts Paypal, and the service cost is about 2$

The only thing you need to prepare in advance is a set of two pairs of keys. You can generate those using this online tool: https://nadejde.github.io/eos-token-sale/

Keep the submitted keys somewhere safe (both public and private) because this is the only piece of data that will allow you to both use and recover your account.

I drop all my projects in /servers/svn/rep/ so, for a while, giving DAV access to /servers/svn/rep/ did the trick. The problem arises when you need to give different permissions to each repository ( and i really didn’t want to write one <Directory> directive for each repository ).

Well, fine-grain permissions ( r/w) per repository using DAV can be accomplished using the SVN AUTHZ. You can allow or deny read or write access to one user or user group by repository.

I’ll post a quick walktrough by my setup, it assumes you already have apache2 rolling with dav_svn_module and authz_svn_module.

Apache Configuration

First of all create a vhost/location for your SVN repo:

<VirtualHost *>
  ServerName    svn.yourhost.com

  <Location />
        DAV svn
        # path to the directory holding your projects repositories.
        SVNParentPath /servers/svn/reps

        AuthType Basic
        AuthName "Subversion Repository"
        AuthUserFile /servers/svn/etc/svn-auth-file
        AuthzSVNAccessFile /servers/svn/etc/svn-authz-file

        require valid-user
  </Location>

</VirtualHost>

This above configuration will provide DAV access to /servers/svn/reps, mapping / to /servers/svn/reps. So, if you have a project called app1 you can acess app1 repository by pointing your browser to http://svn.yourhost.com/app1.

Authentication

We autenticate the users using apache builtin basic auth module. Just create the users file /servers/svn/etc/svn-auth-file using htpasswd command line util.
Let’s add three users to illustrate our example: an app1 coder named Ruth, the server admin “bat” and a guest user.
( Well, unfortunatelly the guest user will also have to have a password )

htpasswd -c /servers/svn/etc/svn-auth-file bat
htpasswd /servers/svn/etc/svn-auth-file ruth
htpasswd /servers/svn/etc/svn-auth-file guest

Authorization

Now we need to limit certain users to certain repositories .This is accomplished by adding some rules to the /servers/svn/etc/svn-authz-file file.
First of all state your user groups by adding the following block to the file:

[groups]
admin=bat
others=guest
coders=ruth

As a fail safe, let’s deny read acess to the base dir to anyone except admins

[/]
* =
@admin = rw

Finally, lets give our coder, Ruth, rw acess to our app1 repository.
Since our app1 is open source, let’s also allow our guest to read from the repository to checkout the latest developments.

[app1:/]
@coders = rw
@others = r
@admin = rw

Just restart your apache and checkout app1 by typing:
$ svn co http://svn.yourhost.com/app1/trunk

I’ve bumped into several issues with the makefiles and the packaging itself but, for sometime now, i’ve a recipe to create a fully cpan compliant distribuition without any manual editing of the non-code distribution files.

First of all create the skeleton of the distro using Module::Starter

module-starter -mb -module=Foo::Bar --author="your name" --email=your@email

This will create your distro structure in the Foo-Bar directory.
Your code will live in the Foo-Bar/lib dir, and the tests in the Foo-Bar/t

Note: the -mb option tells module-starter to use Module::Build instead of ExtUtils::MakeMaker. This materializes in you ending up with a Build.PL script instead of the traditional Makefile.PL. Just remove -mb option if you want a Makefile.PL but ExtUtils::MakeMaker has some quirks that i personaly don’t like so i use Module::Build

Edit Build.PL file in the Foo-Bar directory, it should be similar to this:

#!/usr/bin/perl

use strict;
use warnings;

use Module::Build;

Module::Build->new(
        module_name => 'Foo::Bar',
        license => 'perl',
        requires => {
                'Other::Module' => '0',
        },
        build_requires => {
                'Test::More' => 0,
        },
        create_makefile_pl => 'traditional',
        sign => 0,
)->create_build_script;

The important bits are the ‘requires’ key, wich states all the depencies for you module and the ‘build_requires’ that states extra dependencies to build the module ( including running the tests you ship with the distro )

You can also sign the distro with pgp (which i recommend), just flip the ‘sign’ value to 1.

Now you just have to create the buld script

$ perl Build.PL

and create the first distribution package

$ ./Build dist 

You should have the Foo-Bar-0.01.tar.gz ready to drop on cpan.

I’m now using a completely new set of tools. The design also took a revamp, it’s a simpler, css based, layout which makes it simpler to distribute to all the different pieces of the site.

For the information sitting in my laptop i don’t want traditional disaster and recovery backups, i want to be able to, quickly, search and restore any version of ( virtually ) any file.

Tthe problem? i don’t own a mac.

The principle of the thing:

Incremental backup of all the files that changed in a short period of time ( let’s say 5 minutes, apple’s time machine does it every hour ).
Create a snapshot of your laptop at the backup time, this implies being able to browse the laptop the exact same way that you browse your current file structure

My current setup:

BACKUPDIR="/backups"
DIRSTOBACKUP="/home /data"
date=`date "+%Y-%m-%dT%H:%M:%S"`
rsync -aP --exclude-from=~/backup.exceptions \
     --link-dest=$BACKUPDIR/current $BACKUPDIR/back-$date $DIRSTOBACKUP

cd $BACKUPDIR; rm -f current ;ln -s back-$date current