How to download surge.sh repository? I deployed application, then lost code. How to recover it from surge.sh? Github repository was not updated.
Until 2016, it was not possible: https://github.com/sintaxi/surge/issues/192
Related
I have a Windows Server 2012 with an active repository on VisualSVN version 3.3.1.
We want to copy this to a new VisualSVN Server instance version 5.1.0 on a Windows Server 2019 and replace the old server.
Is there a way to duplicate the repository completely and with all permissions etc. and import it on the other server?
We have already done it with the commands
svnadmin dump REPOS_PATH [-r LOWER[:UPPER]] [--incremental] [--deltas]
and
svnadmin load REPOS_PATH [-r LOWER[:UPPER]].
However, it does not retain the permissions and locks here.
Also, I found a post saying to only copy the files in the repository directory but I am not sure whether this is the right and correct way: Post
Migrating VisualSVN Server
You don't need to use svnadmin dump and svnadmin load when migrating VisualSVN Server onto a new server computer.
You should not mix up the server migration and upgrade tasks. They have to be approached separately if you plan to migrate the server and all repositories from one computer to another. Normally, you need to either to upgrade your existing server installation to the latest version and then upgrade, or upgrade you existing server installation and upgrade later.
Migration instructions are given in the article KB166: Migrating VisualSVN Server to another computer.
Upgrade instructions are given in the article KB204: Upgrading to VisualSVN Server 5.1.
Migrating a repository
You don't need to use svnadmin dump and svnadmin load when importing only one or a few repositories onto another VisualSVN Server installation.
If your task is to migrate the server with all the repositories, see the section above.
When you want to import an individual repository from another server installation (without needing to migrate the server itself and all other repositories), you need to follow the instructions from the article KB10: Importing Repositories into VisualSVN Server:
Create a backup of the repository and restore it on the new computer.
or
Copy the directory of the individual repository onto a new computer and import it.
Repository settings including user permissions and hook scripts will be retained with both approaches.
Is there a way to automate storing code updates to GitHub after a developer publishes a new version of code from Visual Studio (2017 or 2019)?
Or is there a way to automate storing code updates to any code repository?
We also currently use VisualSVN, but are open to other repository software packages if they solve this problem for us.
We publish web projects and console apps to on-prem servers, so my understanding is that GitHub Actions won't work for us (yet).
If you are pushing to an on-premise Git repository hosting server, you can add to that remote repository a post-receive hook.
Said hook can in turn analyze what just got pushed and push it in turn to GitHub.
See git-post-receive-hook-push-to-mirrors as an example of such hook.
We have an on-premise infrastructure with git repository, a CI server and an artifact repository. We are using gradle in our project. This is working perfectly fine for our regular CICD processes.
We are planning to move our code to cloud using private Github and Travis-CI for CI. The problem is that we have a couple of third party jars that are not available in any artifact repositories on the internet, e.g. maven central and others. The on-premise infrastructure worked fine as we had manually installed those jar files in our internal artifact repository.
Our builds on travis are now failing. What is the best way to provide these third party jars to travis during build time?
P.S.: The third party jars are drivers provided by some of our vendors. These are not open source and cannot be pushed to artifact repositories on the internet.
I'm building few scala libraries and use them in business projects. To share libraries i use 'publishLocal' in sbt. This command uploads artifacts into my local folder. This is ok, it's fast but when i work from another machine i have to republish all this libraries because some changes had been made. So, this my is question: Is my workflow correct? Or i have to publish my artifacts to remote binary repository (ex. nexus) and add it to my business projects as resolvers? Should i use 'publishLocal' at all?
As indicated in the comments, it is strongly suggested to use a Repository Manager such as Nexus Repository Manager, or Artifactory.
You might try Nexus Repository Manager 3.x, as it should help quite a bit with your problem. You can install it on your server, as well as locally if you'd like as it can be used with other tools such as npm, NuGet, etc...
You can download the Open Source Software Edition of Nexus Repository Manager from this link: https://www.sonatype.com/download-oss-sonatype
I am working on Automated Build using maven and Jenkins. I am looking for best open source Repository Management for Maven. So that I can have an integaration between Maven and jenkins via respository manager.
You have at least four choices:
Nexus
Artifactory
Apache Archiva
Reposilite
Each has pros and cons. I'd go with Nexus since it is backed by Sonatype who are also involved in Maven development. I liked the Artifactory UI though.
Both Nexus and Artifactory have supported professional editions as well.
These are linked from the maven site as well.