I created a ssh key I then attempted to add the key to the SSH authentication agent and got this error because I named the ssh key a non conventional name (id_gitlab_selectiont), the following steps are required now we good
Development
appending all passed arguments to another command
this will cause problems because of the double quotes
WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!
https://levelup.gitconnected.com/how-to-deal-with-the-remote-host-identification-has-changed-message-with-github-1dea015dae8d or
Install Gitlab
https://docs.gitlab.com/ee/install/docker.html the default username is root, now lets get the default password {container name} being the name of your container lets create a access token Creating SSH keys to push since I named the ssh key a non conventional name, I must put the host in the ~/.shh/config file
Backup gitlab docker
https://copdips.com/2018/09/backup-and-restore-gitlab-in-docker.html
mount: wrong fs type, bad option, bad superblock on
if there is already data on drive that you don’t care about it. format the drive https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-using-volumes.html then mount
bin field not being respected when installing custom npm package
https://github.community/t/npm-bin-field-is-not-exported-in-published-metadata/128402 If i install from registry.selectiont.com the bin property works correctly, but if i install from gitlab, the executable does not get symlinked I had to publish scripts-root to another registry so it could work https://gitlab.com/gitlab-org/gitlab/-/issues/275992 upgraded to 14.7.7-ce.0 and it worked
npm publishing package process
when you want to publish a package to a specific registry, you have to login to that registry first or have a token handy. lets look at logging in first after putting in your user name and password, they will assign you a token and place it in /{user}/.npmrc (/root/.npmrc)[…]
Cross-account pass role is not allowed.
I grabbed an example off the internet and left the arn number.