We have a small dev team of 3 growing to 5 very soon, we currently have a file in git with our database changes. We have local instances of mysql on our machines, on our staging server running jenkins and live.
What are the best practices for keeping databases in sync with code base changes across all stages of development? What are the best tools for version control? Do you have any advice on implementation? Are there any good websites/books/videos that you can recommend?
Many thanks
Something like this maybe?
Hi, I am a current intern at an Salesforce consulting company. I am learning about Salesforce and I have a question in regards to Salesforce Orgs. If I have a Scratch Org and I finish testing and development and I want it to be pushed to production. Do I push the scratch org to a production org? Or does the scratch org turn into a production org? Many thanks if I am totally getting this wrong and for correcting me
> Could not load file or assembly 'Microsoft.Owin.Security' or one of its dependencies. The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020)
I'm getting this sort of error almost every time I start debugging through Visual Studio's debugger using IIS Express. The errors are always the same. Couldn't load file or assembly x or one of its dependencies... Almost always the file or assembly in question is different from the previous time when the exception occurred.
Writing this post, its occurred to me that the problem has only happened since I started using Visual Studio 15 Preview 2 though if that's got nothing to do with it, then is it possible this is something that IIS Express is doing weird?
Could this impact my site when I upload it to the production server?
Hi all. I'm building an app which runs in the browser, but I'm doing some unit testing of my logic in NodeJS (using Tape). As such, I now have some code added to my app code base which is needed only for testing/development, as in the code snippet below. In that code snippet, the else{} portion of the conditional is really needed only for testing/development. Is this mixing-of-testing-and-production-code the correct way to structure my testing? Or should I be organizing things a bit differently, to perhaps keep testing code completely separate from production?
Something about having development-only code mixed in with final production code seems like I'm going about this the wrong way. If so, what are typical ways to resolve the issue? Maybe during development/testing I can assign some debug variable to true, and if so, all my development/testing code is properly inserted/called?
Thanks in advance.
My Code
let functionConstants = {}
if (typeof constants !== 'undefined' && constants) {
// If constants{} has already been set, it means code is running in a browser, so I can easily assign functionConstants = constants.
functionConstants = constants
} else {
// If constants{} has not yet been set, it means code is running in Node, so I have to first require the file constants.js, then assign functionConstants to that value.
functionConstants = require('./constants.js').constants
}Prototyping can get expensive fast and free DIY options only go so far. How much should you realistically spend on a prototype for smoke testing and customer development purposes to find out willingness to pay before you engineer an actual product? Thanks
This is the fifth article in the Modern Web Development Setup series by Kontena Community blogger Juha Kärnä.
Introduction In this article we'll continue setting up the CI/CD system. We'll setup Kontena-based acceptance testing environments into UpCloud and configure them into our Shippable CI/CD pipeline.
Acceptance Test Environment Setup New Kontena Environment Creation To start with, we'll create acceptance testing CI (atci) and acceptance testing environments. The atci environment is meant for running automated acceptance tests and the acceptance testing environment is meant for manual acceptance testing:
$ kontena grid create atci
$ kontena upcloud node create --grid atci --username
<upcloud_username> --password <upcloud_password> --ssh-key
~/.ssh/id_rsa_upcloud.pub --zone de-fra1
$ kontena grid create acceptance-testing
$ kontena upcloud node create --grid acceptance-testing --
username <upcloud_username> --password
<upcloud_password> --ssh-key ~/.ssh/id_rsa_upcloud.pub --zone
de-fra1
We'll follow the setup according to the test environment setup in previous articles. We'll set up the acceptance testing environments under at. and atci. subdomains.
Before integrating the environments with the CI/CD it's good to make sure everything is working as expected by making a manual deployment after everything is set. So at this point we'll write the needed variables into the Vault using the acceptance-testing-ci and acceptance-testing grids. We'll also configure the DNS records, setup Let's Encrypt certificates and make sure the services work well after manual deployments.
Acceptance Tests Tech Selection and Setup
There are several viable tech choices for implementing automated acceptance tests for JavaScript applications. Selenium based solution are quite popular, but there are also interesting alternatives like Nightmare.js. Nightmare.js uses Electron under the hood, supports headless mode and runs tests very fast compared to many other solutions. It's also quite an independent package and simple to setup for the environments we're using. It has some limitations - it's not possible to run the tests with different browsers out-of-the-box, for example - but in this project those are not major limitations.
Some frameworks support generic languages like Gherkin language to define the tests while some use their own DSL. I really like the idea of writing the tests usin
... keep reading on reddit ➡
I was hoping to get /r/sysadmin's professional opinion on accomplishing the following:
I have a publicly facing production server I wish to mirror exactly to VMs such that we can test updates/develop without harming the real thing (which is physical and no intent to virtualize)
Currently I've used clonezilla to make an exact copy of it to a virtual machine but that obviously was never a long term solution. I know rsync exists but... it feels very wrong to have such a privileged account to rsync everything from files to configs even if it is key based.
tl;dr Thoughts on how I can replicate exactly a CentOS server with MySQL to a VM in a secure/sane fashion to test code/updates?
Currently there is no testing/development environment because we are a team of two. My boss was thinking of having my testing environment on my local machine, then push the finish code to production. He does not want to pay for another CF license if it's just me using it. He makes a valid point.What are your suggestions fellow Redditors?
