An Azure cloud product FrontAccounting: Accounting on the Website powered by Niles Partners. FrontAccounting (FA) is a professional web-based Accounting system for the entire ERP chain written in PHP, using MySQL. It is an accounting software solution that can also cover the entire supply chain. For sales, the program can handle all customer accounts, issue quotes and sales orders, send out invoices, and receive payments. If you need to buy things, you can submit purchase orders, maintain supplier accounts, and send out payments. Additionally, you can manage your inventory by setting reorder levels and configuring profiles for each item. Lastly, FrontAccounting ERP works with all your general ledger entries and can generate financial reports. It is a non-profit organization that was founded in 2005. The group primarily relies on donations.
We are launching a product which will configure and publish FrontAccounting embedded pre-configured tool with LAMP and ready-to-launch Machine Image on Azure cloud that contains FrontAccounting, Apache, MySQL, Linux, PHP (LAMP).
Hardware management, including associated contracts: computers (with automated information feeds if combined with OCS-NG or Fusion Inventory), devices, printers, network components and consumables; Support functions: with or without user access, detailed user rights management, automated notifications with personal sable templates, and SLAs; Substantial expandability thanks to its plug-ins: integration with supervision software, project management, new inventory items, etc.
The principal functionalities of the application are:
Features
Sales And Accounts Receivables
Purchases and Accounts Payable
Inventory and Stocks
Manufacturing
Cash and Bank
General Ledger
Reports
Access Levels and adaptations
Multi-Currency Support
Advanced GST/VAT handling
Language Support
It will take a few minutes for your VM to be deployed. When the deployment is finished, move on to the next section.
Connect to virtual machine
Create an SSH connection with the VM.
bashCopy
ssh azureuser@10.111.12.123
Usage/Deployment Instructions
Step 1: Access FrontAccounting in Azure Marketplace and click on get it now button.
Click on continue and then click on create,
Step 2: Now to create a virtual machine, enter or select appropriate values for zone, machine type, resource group and so on as per your choice.
click on Review+create.
Once your Deployment is complete,
To access the application:
Step 1: Use the browser to access the application at http://<instance ip address> Replace instance ip address with the actual IP address of the running instance,
Your installation dialogue will appear.
Click on continue with setup.
Step 2: For setting up Mysql use the following;
Host – localhost
Username – root
Db name – frontaccounting
Db password – Niles@123
Port – 3306
Click on continue with setup.
Step 3: Fill in the details as per requirement and click on install.
Step 4: Your frontaccounting is installed and click on here to start.
Step 5: Fill in admin details and click on login.
Enjoy your application.
Until now, small developers did not have the capital to acquire massive compute resources and ensure they had the capacity they needed to handle unexpected spikes in load. Amazon EC2 enables any developer to leverage Amazon’s own benefits of massive scale with no up-front investment or performance compromises. Developers are now free to innovate knowing that no matter how successful their businesses become, it will be inexpensive and simple to ensure they have the compute capacity they need to meet their business requirements.
The “Elastic” nature of the service allows developers to instantly scale to meet spikes in traffic or demand. When computing requirements unexpectedly change (up or down), Amazon EC2 can instantly respond, meaning that developers have the ability to control how many resources are in use at any given point in time. In contrast, traditional hosting services generally provide a fixed number of resources for a fixed amount of time, meaning that users have a limited ability to easily respond when their usage is rapidly changing, unpredictable, or is known to experience large peaks at various intervals.
Traditional hosting services generally provide a pre-configured resource for a fixed amount of time and at a predetermined cost. Amazon EC2 differs fundamentally in the flexibility, control and significant cost savings it offers developers, allowing them to treat Amazon EC2 as their own personal data center with the benefit of Amazon.com’s robust infrastructure.
When computing requirements unexpectedly change (up or down), Amazon EC2 can instantly respond, meaning that developers have the ability to control how many resources are in use at any given point in time. In contrast, traditional hosting services generally provide a fixed number of resources for a fixed amount of time, meaning that users have a limited ability to easily respond when their usage is rapidly changing, unpredictable, or is known to experience large peaks at various intervals.
Secondly, many hosting services don’t provide full control over the compute resources being provided. Using Amazon EC2, developers can choose not only to initiate or shut down instances at any time, they can completely customize the configuration of their instances to suit their needs – and change it at any time. Most hosting services cater more towards groups of users with similar system requirements, and so offer limited ability to change these.
Finally, with Amazon EC2 developers enjoy the benefit of paying only for their actual resource consumption – and at very low rates. Most hosting services require users to pay a fixed, up-front fee irrespective of their actual computing power used, and so users risk overbuying resources to compensate for the inability to quickly scale up resources within a short time frame.
No. You do not need an Elastic IP address for all your instances. By default, every instance comes with a private IP address and an internet routable public IP address. The private address is associated exclusively with the instance and is only returned to Amazon EC2 when the instance is stopped or terminated. The public address is associated exclusively with the instance until it is stopped, terminated or replaced with an Elastic IP address. These IP addresses should be adequate for many applications where you do not need a long lived internet routable end point. Compute clusters, web crawling, and backend services are all examples of applications that typically do not require Elastic IP addresses.
You have complete control over the visibility of your systems. The Amazon EC2 security systems allow you to place your running instances into arbitrary groups of your choice. Using the web services interface, you can then specify which groups may communicate with which other groups, and also which IP subnets on the Internet may talk to which groups. This allows you to control access to your instances in our highly dynamic environment. Of course, you should also secure your instance as you would any other server.