AppFog

Author: n | 2025-04-25

appfog-setup appfog-tutorial appfog-download appfog-features appfog-review appfog Updated ; marianomorriswyw / AppFog Star 0. Code Issues Pull requests

appfog/af: AppFog's command line client - GitHub

According to a source within the company, CenturyLink is acquiring AppFog, a platform-as-a-service company. Terms of the deal were not revealed.AppFog will become part of Savvis, a Century Link company that offers cloud infrastructure and hosted IT services. Savvis did not reply to requests for comment about the acquisition. AppFog Co-Founder and CEO Lucas Carlson would also not comment about the deal.AppFog is a Platform as a Service that can be integrated on-premise into a company’s data center. It is also available as a public service. The company was originally founded as PHPFog before changing its name early in 2011 after receiving $8 million in funding. In August of last year, AppFog acquired Nodester, a Node.js platform. Since last year, the company began focusing more on a private PaaS strategy. AppFog competes in a crowded market that includes Pivotal’s Cloud Foundry, Red Hat’s OpenShift, ActiveState’s Stackato and Apprenda. Heroku and Engine Yard are two of the leaders in the public PaaS market.For Savvis, the AppFog deal is a move to extend beyond being a pure infrastructure play. AppFog will help the company move its offerings higher up the stack, differentiating by appealing to enterprise developer teams who have increasing buying power in the booming app economy.The deal makes sense, considering that earlier this week, a Savvis spokesperson sent me a pitch asserting that Savvis would be making a major PaaS announcement next week at GigaOm’s Structure conference. The email from the spokesperson said the news would “shake up the cloud industry.”I’m not so certain about that shake up. AppFog is a smaller PaaS player and Savvis faces tough competition from Amazon Web Services, Windows Azure and a number of other companies including AT&T, Terremark and Sungard. Most Popular Newsletters Subscribe for the industry’s biggest tech news Related ServerWatch content and product recommendations are editorially independent. We may make money when you click on links to our partners. Learn More.The market for Platform-as-a-Service (PaaS) solutions is one that is rapidly becoming highly competitive, as companies new and old aim for their slice of the emerging market.Startup formerly known as PHP Fog receives new funding as it expands into the PaaS server space.Portfland, Oregon based startup AppFog is among those that are trying to grab PaaS share. Until this month, AppFog was known as PHP Fog and focused exclusively on providing a PaaS solution for PHP developers and servers. The company is now expanding beyond just PHP with a PaaS platform for multiple languages including Ruby, and Java. The expansion is being fueled by $8 million in Series B investment led by Ignition Partners. In total, AppFog has raised $9.8 million in funding to date.“We’re not moving away from PHP,” AppFog CEO Lucas Carlson told InternetNews.com. “The new funding gives us the opportunity to broaden our scope and take to other technologies what we’ve built for PHP.”What AppFog has built is an easy access ramp for PHP developers to deploy their applications in a multi-tenant, elastic cloud model. Carlson explained that currently the AppFog technology is hosted on Amazon’s EC2, and also noted that the service can move to other clouds.“We built it from day one not to care about the underlying infrastructure,” Carlson said. “So now that we have more resources we can deliver on that promise.”In terms

GitHub - difio/difio-appfog-python: Difio registration agent for AppFog

Of what the underlying technology is behind AppFog, Carlson didn’t spare too many details. He noted that the system is using the latest version of PHP, Apache and MySQL. They are also using the ngnx server as well as Varnish for caching. Carlson said that on top of those open source components is a proprietary system that AppFog has been developing. He added that AppFog will be providing additional details on the platform in the next couple of months.The AppFog system already provides an integration point for developers.“If your IDE supports version control through GIT, then it’s a push/deploy action,” Carlson said. “We have been talking to Adobe about tighter integration, but just having the source control support is a pretty good start.”The market for PaaS solutions is a crowded one already with Red Hat’s OpenShift and VMware’s Cloud Foundry all pushing their respective vision for PaaS. Carlson isn’t too worried about competition at this point.“It’s a greenfield market and there is a lot of open space,” Carlson said. “And because it’s such an open space, we’ve chose to focus on what we’re good at, namely user experience.”Sean Michael Kerner is a senior editor at InternetNews.com, the newsservice of Internet.com, thenetwork for technology professionals.Follow ServerWatch on Twitter. appfog-setup appfog-tutorial appfog-download appfog-features appfog-review appfog Updated ; marianomorriswyw / AppFog Star 0. Code Issues Pull requests appfog-setup appfog-tutorial appfog-download appfog-features appfog-review appfog Updated ; Improve this page Add a description, image, and links to the

AppFog Private PaaS for the Enterprise

Container you can’t reach, or one that doesn’t have the right firewall rules in place. The Write-Once-Run-Anywhere promise of Docker is a promise made to the Developer. The “Anywhere” on which it runs must still have the right processor architecture, host operating system, surrounding network, policy, governance, chargeback, and all the other requirements of running an actual service. This is not meant to be a ding on Docker, or AppFog, or any of them. It just highlights the two populations, and the need for a comprehensive solution. There are very few solutions out there (if any) that can effectively speak to both groups in their native languages.Cisco Prime Service CatalogThe need for rapid deployment, whether it be continuous delivery or self-service, is bringing these two audiences closer to one another. This alignment will serve everyone well in the future as applications expand in complexity and capability under continuous pressure to reduce cost.However, we still have a ways to go and at least part of problem comes from the different context/view-points of the various groups involved. Most infrastructure & operations teams do not readily understand the AppFog, lighter-than-VM, container concept. Developers, on the other hand, get AppFog right off the bat and fail to understand why they would still need virtual machines, physical infrastructure, network configuration, or tools like Cisco Prime Service Catalog.Containers need to go somewhere and run on something (just like JVM runs in an OS), and this somewhere/something is the infrastructure (virtual or physical). Container systems are only going to be as stable as the underlying infrastructure, and both the container layer and the infrastructure layer need to be managed (and automated and governed by policy, etc.). And while containers are currently the latest hot topic, there’s likely to be mixed adoption with more traditional IaaS for some AFThe AppFog CLI. This is the command line interface to AppFog.comaf is based on vmc but will have features specific to the AppFog service as well as having the default target set to AppFog's serviceInstallationThere are two ways to install af. Most users should install the RubyGem.You can also check out the source for development. You will need Bundler to build af.$ git clone cd af$ bundle installUsageCopyright 2010-2012, VMware, Inc. Licensed under theMIT license, please see the LICENSE file. All rights reserved.] [command_options]Try 'af help [command]' or 'af help options' for more information.Currently available af commands are:Getting Started target [url] Reports current target or sets a new target login [email] [--email, --passwd] Login info System and account informationApplications apps List deployed applicationsApplication Creation push [appname] Create, push, map, and start a new application push [appname] --infra Push application to specified infrastructure push [appname] --path Push application from specified path push [appname] --url Set the url for the application push [appname] --instances Set the expected number of instances push [appname] --mem M Set the memory reservation for the application push [appname] --no-start Do not auto-start the application push [appname] --label Add specified label to app revision recordApplication Download pull [path] Downloads last pushed source to or [path]Application Operations start Start the application stop Stop the application restart Restart the application delete Delete the applicationApplication Updates update [--path] [--label] Update the application bits, with optional revision label mem [memsize] Update the memory reservation for an application map Register the application to the url unmap Unregister the application from the url instances Scale the application instances up or down rename Change the application's nameApplication Information crashes List recent application crashes crashlogs Display log information for crashed applications logs [--all] Display log information for the application files [path] [--all] Display directory listing or file download for path stats Display resource usage for the application instances List application instances history Show version history of the application diff Compare current directory with deployed application hash [path] [--full] Compute hash of directory, defaults to currentApplication Environment env List application environment variables env-add Add an environment variable to an application env-del Delete an environment variable to an applicationServices services Lists of services available and provisioned create-service [--name,--bind] Create a provisioned service create-service --infra Create a provisioned service on a specified infrastructure create-service Create a provisioned service and assign it create-service Create a provisioned service and assign it

Appfog Deployer for Hexo GitHub

Replace and with your actual values, while your cloud name is already correctly included in the format. When using Cloudinary through a PaaS add-on (e.g., Heroku or AppFog), this environment variable is automatically defined in your deployment environment. For example:Append additional configuration parameters, for example upload_prefix and secure_distribution, to the environment variable:Setting configuration parameters globallyHere's an example of setting configuration parameters globally in your Python application:You must set your configuration parameters globally before importing the cloudinary.uploader and cloudinary.api classes in order to pass the optional api_proxy configuration parameter successfully:Python configuration and installation video tutorialWatch this video tutorial to see how to install and configure the Python SDK:Tutorial contentsPython capitalization and data type guidelinesWhen using the Python SDK, keep these guidelines in mind: Parameter names: snake_case. For example: public_idClasses: PascalCase. For example: CloudinaryFieldMethods: snake_case. For example: add_tagPass parameter data as: dict or named argumentsFull Flask demo app and code sandboxThis demo uses Cloudinary's auto-tagging feature to recommend product images based on the images you select. Try out the demo and then check out the code behind it. This code is also available in GitHub.Read this blog to discover all the Cloudinary features in this demo. Jupyter notebookThis Jupyter notebook focuses on uploading images to your product environment. It walks you through: Installing and configuring Cloudinary.Creating an upload preset.Applying the preset to assets being uploaded.Uploading assets with incoming transformations.To run the code snippets in the Jupyter notebook, you'll need to enter your credentials as part of configuration. Find your credentials on the API Keys page of the Cloudinary Console Settings.Sample projectsFor additional useful code samples and learn how to integrate Cloudinary with your Python applications, take a look at our sample projects on GitHub and our Python sample projects docs. Basic python sample: Uploading local and remote images to Cloudinary and generating

Memcached Cloud on AppFog GitHub

Infrastructure matters. It’s the foundation on which everything else in IT is built. The purpose of data center infrastructure is to run applications, yet the relationship between infrastructure admins and application developers is often dismal.Are you an infrastructure admin? When’s the last time you talked to an application developer? Did you need a secret decoder ring for the terms they used? I bet they felt the same way. Developers often know exactly what kind of infrastructure they want and infrastructure admins are typically tasked with finding out what kind they actually need. That can be a tough conversation even without the language barrier.Do your developers talk about AppFog? Sounds like something you might use to obfuscate code. Or maybe an app that helps you navigate San Francisco in the summer.How about Docker? That’s a brand of comfortable, business casual trousers, right? Have you seen the Harbaugh commercial?Did they ask about the network? Probably not. The average developer may view the network as, a) the clippy plug that goes into the side of a laptop, b) a WiFi SSID, or c) is something that starts with an inscrutable code like “3G,” “GSM” or “LTE”. They just want their app to be connected.Have you heard a developer say, “VMs are heavy?” I have and I love this one. VM templates can become bloated as our definition of a standard baseline continues to expand. It’s sort of the nature of all things tech.LOL. Cats.Did they mention CI or CD? I thought it might have something to do with music… or a disease. However my colleagues assure me that Continuous Integration and Continuous Deployment aren’t dangerous or contagious. I’m still not sure. Better wear a helmet.All this conversation leads to what some call enterprise platform-as-a-service (PaaS) and others call IaaS+. In talking with enterprise. appfog-setup appfog-tutorial appfog-download appfog-features appfog-review appfog Updated ; marianomorriswyw / AppFog Star 0. Code Issues Pull requests

Deploying An Application To AppFog - YouTube

Customers, two primary audiences have emerged: Developers and SysAdmins. These two audiences speak very different languages and come at the problem from very different perspectives. In truth, it’s a continuation of the divide between IT Infra/Ops and IT’s internal customers (application developers), but adapted to the new cloud world.Starting with a top-down view from a developer’s perspective, there’s immense interest in anything that speeds up the development process. CI and CD remain popular topics but more recently the developer community has started discussing “lighter-than-VM” containers such as OpenShift, Docker, Cloud Foundry (and derivatives like Pivotal, AppFog, and Stackato). The value can be crudely summed up as Use-Any-Language and Write-Once-Run-Anywhere using a “container” as an abstraction mechanism. To further oversimplify, I like to think about these containers as beefed up Java virtual machines (JVMs). Docker uses a shipping container analogy.In most containers you can write in many different languages, you can move your app from container to container across machines, and you can deploy your app multiple times into one or multiple containers; even on the same machine and at the same time for horizontal scale and resilience. Generally no data is stored in there so you have to use something like external block storage accessed from your app via URIs, and that’s how you ensure data persistence and consistency across app instances. Of course we’re just scratching the surface, as there is a lot of other management and instrumentation options such package plug-ins (like a message bus for example).Starting at the bottom with the infrastructure, SysAdmins from IT infrastructure & operations teams often don’t worry about app development. App development is something that occurs on a laptop or desktop, using Eclipse or Visual Studio (Emacs, anyone?). Eventually code is compiled and built and pushed to a server somewhere. But which