alexbeletsky / alexbeletsky.github.io Goto Github PK

http://beletsky.net/2013/09/playing-with-dokku-on-vagrant.html

$ cat ~/.ssh/id_rsa.pub | ssh [email protected] "sudo gitreceive upload-key alexanderbeletsky"
Permission denied (publickey).

I decided I could get around that by logging in via vagrant ssh and copy and pasting the key.

But then I found gitreceive wasn't yet installed in the vm. I installed it, then it complained:

/usr/local/bin/gitreceive: line 38: /home/git/.ssh/authorized_keys: No such file or directory

I created the directory and ran the upload-key command, seemed to work.

I went back to my host shell and tried to push to the dokku vm...

Permission denied (publickey).
fatal: Could not read from remote repository.

Now I backtrack and look at the dokku main github readme page - there's no mention of gitreceive. Instead they give a similar command:

$ cat ~/.ssh/id_rsa.pub | ssh progriumapp.com "sudo sshcommand acl-add dokku progrium"

It's not clear whether dokku and progrium are both arbitrary names and I can invent my own or not.

Looking at the readme for sshcommand it looks like I should first sshcommand create a user anyway... but against which command? Or has the dokku bootstrap script created a dokku user for dokku's own special command and therefore only the 'progrium' is arbitrary?

Either way I still can't push to the dokku vm.

Reading the last item here: https://github.com/progrium/dokku/wiki/Troubleshooting I wonder if it's because I had copied my public key from ~/.ssh/id_rsa.pub as instructed, but the Vagrant vm is using it's own generated key at ~/.vagrant.d/insecure_private_key

No public key there though. I generated one with ssh-keygen -y and gave that to sshcommand, but really I'm just trying random stuff at this stage.

Contributions to this question are here: http://stackoverflow.com/questions/32127269/npm-scripts-nodemon-watching-js-and-scss-files-for-changes

http://beletsky.net/2015/04/npm-for-everything.html

Great tutorial, definitely will be using this process in the future. One thing tho, the nodemon watch doesn't seem to work - is this deprecated?

If I remove the single quotes around the 'npm run build-sass' & 'npm run build-js' and use double quotes
"watch-js": "nodemon -e js -w public/js -x \"npm run build-js\""
"watch-sass": "nodemon -e scss -w public/sass -x \"npm run build-sass\"",
it doesnt throw an error, but it doesn't trigger the commands

But if I keep it as is (in the tutorial) I get the following message in red writing
[nodemon] app crashed - waiting for file changes before restarting
Its also doesn't trigger the commands

The following post is outdated according to the newer NancyFX version (1.2.0.0).
I was getting a compilation error in the JsonNetSerializer because a Extensions property was missing and after that I get a runtime exception:

An unhandled exception of type 'System.ArgumentException' occurred in Nancy.dll

Additional information: types: The same implementation type cannot be specified multiple times for Nancy.ISerializer

TestProject.JsonNetSerializer

To solve that I change the bootstrapper code to that:

        protected override NancyInternalConfiguration InternalConfiguration
        {
            get
            {
                return NancyInternalConfiguration.WithOverrides(
                    c =>
                        {
                            c.Serializers.Remove(c.Serializers.FirstOrDefault());
                            c.Serializers.Insert(0, typeof(JsonNetSerializer));
                        });
            }
        }

I dont know if this is the best approach right now but its working here.

What you think?

Hi there, I am trying to get your http://beletsky.net/2013/11/simple-authentication-in-angular-dot-js-app.html app to work, but keep getting:
Error: authorization.login(...) is undefined
which is being called in the auth.js...
any ideas?

In your footer you link to the issues list

...e on <a href="https://github.com/alexanderbeletsky/site/issues">github</a>.

You renamed your repo, so this link leads to a 404.