What is the current best practice for maintaining repository of proprietary Python packages in Azure such as for use in Azure Notebooks or for building Python-based web apps?
I am hoping for MS to pick this one up to see if they have something in the works that would help integrate Python environments and package repos with Notebooks better.
Their docs only address how to install something into the main environment.
https://notebooks.azure.com/help/jupyter-notebooks/package-installation/python
Related
How to import and run Apache NiFi using eclipse IDE. There is no documentation for development purpose, as I wanted to change the source code for UI related. Is there any guide for import and run Apache NiFi(maven project).
Below is the project structure where nifi is the parent directory and all are its module. So, how can I run run using eclipse, run configuration required.
I just wanted to modify the whole NiFi UI.
There is a very extensive Developer Guide with discussion around common development patterns and problems, a Contributor Guide with instructions for cloning the git repository and importing the code into various development environments, and I have done presentations on developing custom processors. Do these not address your questions? We are always welcome to feedback on how to improve documentation and ease of use.
Troposphere is a python project for AWS provisioning. This is a mature project.
AWS CDK is still in developer preview.
cdk diff does help on ease of state maintenance before cdk deploy. Am not sure, how troposphere helps us on state maintenance? except generating a cloudformation template...
From AWSEvent talk, it is mentioned that, abstractions are not built-in for using Troposphere
where as
AWS CDK has good abstractions.
CDK enables CI/CD, easily, where-as Troposphere needs extra automation to upload CF templates
We need to take a decision on picking one, to provision our infrastructure on AWS
From the aspect of state maintenance, software best practice, code maintenance & supported resource types, CI/CD(end-to-end automation) for provisioning,
What are the advantages of AWS_CDK vs Troposphere vs Stacker? being open to any programming language..
troposphere is part of what CDK does, a more apt comparison would be stacker (https://stacker.readthedocs.io/en/latest/ which uses troposphere -- I'm a maintainer of both) vs CDK. Let me know if you have any other questions!
I have azure subscription. I want to know that how can one setup WebRTC on azure, noticing that it needs node.js and other plugins.
I am using WebRTC example as a startup project.
I want to know how can I make the use of its code, make it work and use its source code.
Download the source files. Use a local git repository and after that push to a Windows Azure Web Site:
http://www.windowsazure.com/en-us/develop/nodejs/tutorials/create-a-website-(mac)/?fb=pt-br
How do I modify the source of an installed package in Heroku? It's a django app, but I suppose it shouldn't make much of a difference?
Heroku uses Git to manage your source code. Please see the quickstart guide at https://devcenter.heroku.com/articles/quickstart.
You will have to install Heroku Toolbelt, which is a command-line tool. With that application, you will be able to manage and deploy your heroku application.
If you ment 3rd-party addons, I think these are submodules, so you may not be able to modify them.
I Develop one website using magento. How to i Publish on server? If asp.net after publishing
codes are converted into dll . but here magento How It work? How i configure my own website?
Thanks in Advance...
There are a number of ways to do this. From simplest to most complex:
Simple zip and unpack on the server. Migrate databases with mysqldumps.
Push files with an FTP program. Preferably one with a compare viewer, such as Beyond Compare
If you utilize a QA environment or a staging site on the same box or a local server you can utilize rsync to push changes from one directory to another.
Create a source-control repository and use your production site root as a checkout of your Magento application (probably your best bet for ease of use).
Utilize source-control but deploy with a build tool such as Apache Ant.
Implement continuous integration with a tool such as Capistrano, Hudson/Jenkins, or CruiseControl
You really want to be using source control anyhow - so deploying straight from SVN/Git/Hg or another tool makes the most sense as it is easiest to manage and requires very little effort on your part. Making your repository publicly accessible can be as easy as using a free service such as GitHub or Beanstalkapp. Paid levels give you private repos or more than one user.
Continuous integration will be your best bet for rapid deployment on a site that is changing quickly and many deployments happen daily. Some comparison of tools:
http://en.wikipedia.org/wiki/Comparison_of_Continuous_Integration_Software
I hope that helps. I have deployed Magento using all of the above methods. There really is no elegant way to push databases around outside of using upgrade scripts in local modules. You can use tools like Maatkit to diff tables or in some extreme situations I've seen developers alternate between qa and production environments using Magento's built-in table prefixes.