Sign Up Now!

Sign up and get personalized intelligence briefing delivered daily.


Sign Up

Articles related to "command"


How to Deploy Streamlit on Heroku

  • For those who don’t know, Heroku is a platform as a service (PaaS) that enables developers to build, run, and operate applications entirely in the cloud.
  • Then once it’s downloaded, just step out of the folder, run the following command, and in the folder, you should find your requirements.txt file.
  • Heroku builds systems using Git and it’s insanely easy to get set up.
  • The first time you do this you’ll need to click here and install the Heroku CLI.We’re using the free version of Heroku which is great but naturally has drawbacks as it doesn’t have certain desirable features configured.
  • The features are more useful for larger projects (like SSL and scalability, also our machines tend to go to sleep if they are idle for more than 30 minutes) but hey, it’s free!
  • I really recommend these pragmatic approaches because without users interacting with your product — you’ll just never know if it’s any good.

save | comments | report | share on


How to Deploy Streamlit on Heroku

  • For those who don’t know, Heroku is a platform as a service (PaaS) that enables developers to build, run, and operate applications entirely in the cloud.
  • Then once it’s downloaded, just step out of the folder, run the following command, and in the folder, you should find your requirements.txt file.
  • Heroku builds systems using Git and it’s insanely easy to get set up.
  • The first time you do this you’ll need to click here and install the Heroku CLI.We’re using the free version of Heroku which is great but naturally has drawbacks as it doesn’t have certain desirable features configured.
  • The features are more useful for larger projects (like SSL and scalability, also our machines tend to go to sleep if they are idle for more than 30 minutes) but hey, it’s free!
  • I really recommend these pragmatic approaches because without users interacting with your product — you’ll just never know if it’s any good.

save | comments | report | share on


How to Deploy Streamlit on Heroku

  • For those who don’t know, Heroku is a platform as a service (PaaS) that enables developers to build, run, and operate applications entirely in the cloud.
  • Then once it’s downloaded, just step out of the folder, run the following command, and in the folder, you should find your requirements.txt file.
  • Heroku builds systems using Git and it’s insanely easy to get set up.
  • The first time you do this you’ll need to click here and install the Heroku CLI.We’re using the free version of Heroku which is great but naturally has drawbacks as it doesn’t have certain desirable features configured.
  • The features are more useful for larger projects (like SSL and scalability, also our machines tend to go to sleep if they are idle for more than 30 minutes) but hey, it’s free!
  • I really recommend these pragmatic approaches because without users interacting with your product — you’ll just never know if it’s any good.

save | comments | report | share on


Troubleshooting OpenShift Clusters and Workloads

  • Unlike the example with nodes, this won’t give you shell to the running pod, but rather create exact replica of the existing pod in debug mode.
  • Another use case would be to copy files into the pod (container) to quickly fix some issue during testing, before fixing it properly in Docker image ( Dockerfile) or source code.
  • First command can inspect image repository, which can be useful for example in case image can’t be pulled, which might happen if the tag doesn’t exist or the image name got misspelled.
  • When everything else fails, you might try running oc adm must-gather to get all the information available from the cluster, that could be useful for debugging.
  • Next, we create carbon copy of the application using oc debug and try reaching the database pod with curl, which is successful.

save | comments | report | share on


The 4 Steps to Branching in Git that Data Scientists Should Know

  • All jokes aside, understanding how and when to branch is critical to working with Git. I’ll walk you through the four-step process I use on my projects.
  • If you work in a group, you may want to designate one person as the repo owner and designated them as the one person that can create a new feature branch.
  • The proper way to patch a tag would be to check out the branch it was derived from and create a new branch from there.
  • This means you would add the patch code to a new v0.1.1-features branch and then merge those changes back into master and tag it as v0.1.1.
  • If the master branch is ahead of the feature branch you are patching; you need to decide if you want to tag from the current branch or merge to master and include those changes in the next release’s tag.

save | comments | report | share on


Troubleshooting OpenShift Clusters and Workloads

  • Unlike the example with nodes, this won’t give you shell to the running pod, but rather create exact replica of the existing pod in debug mode.
  • Another use case would be to copy files into the pod (container) to quickly fix some issue during testing, before fixing it properly in Docker image ( Dockerfile) or source code.
  • First command can inspect image repository, which can be useful for example in case image can’t be pulled, which might happen if the tag doesn’t exist or the image name got misspelled.
  • When everything else fails, you might try running oc adm must-gather to get all the information available from the cluster, that could be useful for debugging.
  • Next, we create carbon copy of the application using oc debug and try reaching the database pod with curl, which is successful.

save | comments | report | share on


The 4 Steps to Branching in Git that Data Scientists Should Know

  • All jokes aside, understanding how and when to branch is critical to working with Git. I’ll walk you through the four-step process I use on my projects.
  • If you work in a group, you may want to designate one person as the repo owner and designated them as the one person that can create a new feature branch.
  • The proper way to patch a tag would be to check out the branch it was derived from and create a new branch from there.
  • This means you would add the patch code to a new v0.1.1-features branch and then merge those changes back into master and tag it as v0.1.1.
  • If the master branch is ahead of the feature branch you are patching; you need to decide if you want to tag from the current branch or merge to master and include those changes in the next release’s tag.

save | comments | report | share on


Troubleshooting OpenShift Clusters and Workloads

  • Unlike the example with nodes, this won’t give you shell to the running pod, but rather create exact replica of the existing pod in debug mode.
  • Another use case would be to copy files into the pod (container) to quickly fix some issue during testing, before fixing it properly in Docker image ( Dockerfile) or source code.
  • First command can inspect image repository, which can be useful for example in case image can’t be pulled, which might happen if the tag doesn’t exist or the image name got misspelled.
  • When everything else fails, you might try running oc adm must-gather to get all the information available from the cluster, that could be useful for debugging.
  • Next, we create carbon copy of the application using oc debug and try reaching the database pod with curl, which is successful.

save | comments | report | share on


The 4 Steps to Branching in Git that Data Scientists Should Know

  • All jokes aside, understanding how and when to branch is critical to working with Git. I’ll walk you through the four-step process I use on my projects.
  • If you work in a group, you may want to designate one person as the repo owner and designated them as the one person that can create a new feature branch.
  • The proper way to patch a tag would be to check out the branch it was derived from and create a new branch from there.
  • This means you would add the patch code to a new v0.1.1-features branch and then merge those changes back into master and tag it as v0.1.1.
  • If the master branch is ahead of the feature branch you are patching; you need to decide if you want to tag from the current branch or merge to master and include those changes in the next release’s tag.

save | comments | report | share on


The 4 Steps to Branching in Git that Data Scientists Should Know

  • All jokes aside, understanding how and when to branch is critical to working with Git. I’ll walk you through the four-step process I use on my projects.
  • If you work in a group, you may want to designate one person as the repo owner and designated them as the one person that can create a new feature branch.
  • The proper way to patch a tag would be to check out the branch it was derived from and create a new branch from there.
  • This means you would add the patch code to a new v0.1.1-features branch and then merge those changes back into master and tag it as v0.1.1.
  • If the master branch is ahead of the feature branch you are patching; you need to decide if you want to tag from the current branch or merge to master and include those changes in the next release’s tag.

save | comments | report | share on