Normally to deploy a packaged component using Boomi platform API, we use a packaged component Id and this end in deploying just one packaged component (whose id is provided). However, I want to deploy a list of packaged components sharing the same package version in one api call, is that possible?
Related
I am newbie to ABP which is based on .net framework and.
I was going through the code of public repository of ABP framework https://github.com/abpframework/abp
my question is: What is the intention behind this code and how do we actually run it and use it as docker image if we want ?
And run it inside my cicd jenkins pipeline.
This directory contains lot of package.json, ps1, ts and json etc files.
project directory
deploy structure inside this directory and framework directory
We have also lot of modules here and what's the use of this ?:
modules structure
Should I create a new project and try to use this repo as some dependency since it looks like some official framework code itself not the actual project.
How we are even using this for micro-service compatible by looking at the official site https://abp.io/?
How we can containerize this app and deploy it on aws ec2 linux machine ?
Will it even support on Linux machine ?
-Thanks in advance
First of all, ABP is a framework as you mentioned and you can't dockerize the framework. Instead, you should create a new startup template/application via CLI or Get Started page.
You can use the following command to create a startup template with MVC as UI and EF Core as database provider.
dotnet tool install -g Volo.Abp.Cli
abp new Acme.BookStore -t app -u mvc --mobile none --database-provider ef -csf
After creating an application, you can dockerize it as you do in a .net core project.
There is a good article (and also video content) about "Deploy a Tiered Application (based on ABP Framework) to Docker Swarm", I suggest you to check it out.
We have also lot of modules here and what's the use of this ?:
ABP Framework is a modular framework and the Application Modules provide pre-built application functionalities. In other words, after you've created an application based on ABP Framework, you can add pre-defined modules to it.
For example: ABP Framework has a module named Docs and https://docs.abp.io/en/abp/latest/Modules/Docs uses this module.
Will it even support on Linux machine ?
After you've created images for your application, you can run it in any OS you want.
I have created my electron app and built it on .deb format using electron-builder. But to enable auto-update, now I have switched into appImage format. But, for desktop integration to work, I have to use an external library as per their documentation.
As of my understanding, every user has to install AppImageLauncher for this to work. I think this is not a good method to distribute my app. Are there any suggestions?
GitHub recently released a container registry alongside their package registry. What is the difference? When would it be better to use one or the other? Do we need both?
Packages are generally simple: they are essentially an archive (i.e. zip file) that contains contents (code libraries, application executables, etc.) and a manifest file (json document, xml file, etc) that describes those contents with a package name and version number (at a minimum).
ie:- npm,pip and composer packages.
Container images are also simple, but they're more like an archive (i.e. a zip file) than a package.
ie:- nginx, redis etc
Verdict:- if some libs repetitively used in any project then we can create package and use in project .while for all project based dependencies we need to choose container to run this. Yes we need both.
After debating this with a Docker-using friend for a while I think I've found a satisfactory explanation:
Packages are for modules of code which are compiled together into an
Application.
Containers are for Applications which are compiled together into a
Server.
This is a bit confused by the fact that a Package can contain a standalone Applications, and Containers will often use package managers like Apt to install these applications. I feel like this is an abuse of package management due to a legacy where we didn't have Containers. Eventually I would expect most Applications will be delivered in Container form.
is there a way to ember Embed/package mongodb installer with electron builder.
I have tried npm/github repos, and find none.
You cannot bundle MongoDB with Electron.
Quoting from this site: https://www.techiediaries.com/electron-data-persistence/
Pros and Cons of Using MongoDB
For the pros of using MongoDB with Electron apps:
Available for all Electron suppored platforms such as Windows, Linux
and MAC. So it doesn't limit the cross platform feature of Electron.
Can be installed and integrated easily with Electron.
There are also some cons:
Can't be bundled with Electron so the end users need to install it
separately from your application.
Overkill for small apps.
There are some other persistent databases you can package with Electron, such as NeDB, that you might consider trying.
I am very new with electron application. I need some help with election installation.
I have an Electron desktop application and a windows service.
I can start and stop my pre installed services by using sudo-prompt package.
I am creating windows installer by using electron-winstaller package.
But I want to bundle my windows service along with my electron application. My requirement is when I install my electron package then it should install my service also, when I uninstall my package then that service should be uninstalled.
Please help me out. Any clue, Any suggestions will be appreciated.
If you think this should be achieved with something else then please do suggest me.
Electron's windows installer packager strikes me a specific case tool that would likely hit limitations in scenarios like this. I would use a general case tool instead such as the Free and Open Source Windows Installer XML Toolset aka WiX. I would also use with that another FOSS application called Industrial Strength Windows Installer XML aka IsWiX.
WiX allows you to describe and build MSI databases using an XML/XSD domain specific language. It supports MSBuild for easy integration with your CI/CD pipeline. IsWiX* is a set of project templates and graphical designers that provide an opinionated project structuring (scaffolding) and greatly speeds up the learning curve and implementation. For example, this installer you describe could be done without writing a single line of XML.
For more information see: https://github.com/iswix-llc/iswix-tutorials
The desktop-application and windows-service tutorials should** show you everything you need to know to author this installer. Basically follow the desktop-application all the way through and then skip to the final portion of the windows-service tutorial where you define the windows service.
I'm the maintainer of IsWiX
** This assumes your service exe is a proper Windows service that interfaces with the windows service control manager. If it's really just a console app that runs as a service you will need to include a program such as srvany.exe. This will require one line of hand crafted XML to extended the service definition in the registry with the proper command line value to be passed to your exe. An example can be found here: Wix installer to replace INSTSRV and SRVANY for user defined service installation