Thursday, July 16, 2015

Upload image to Google Cloud Storage using App Engine [Python]

Today i will show you how you can build app engine service that can handle "POST" requests to save images to "Google Cloud Storage".

The Handler will extract image data from "post" request "base64" and create it on the Cloud Storage




1 - download cloud storage client library from here.
   - i prefer using "git bash" for download it using the following command
   "git clone https://github.com/GoogleCloudPlatform/appengine-gcs-client.git gcs-client" 


2 - goto the "cloudstorage" folder and copy the folder to your project directory. 
   - Path to the folder ==> "\gcs-client\python\src"



3 - open Console Developer and create bucket for storing images.
  


4 - Now we are ready to write some code 
  • I suppose you are familiar with app engine so i will focus on cloud storage only.
  • I'm using PyCharm as IDE. 

5 - Create new python file and name it "UploadImageToCloudStorage,py".


5 - open the file, import "webapp2 - cloudstorage - os - time" libraries and declare your "retry_params".



6 - Create UploadHandler that will handle your post request.


7 - Create "CreateImage" function that will take image name,data, extension and save it to your bucket.


8 - now we need to get the image data and extension from post request :




9 - Now we add the code in our "post method" :-
  1. define bucket variable the will hold your bucket name.
  2. generate unique name for image using "time" library.
  3. combine bucket with image name
  4. invoke "CreateImage" method.
  5. generate a link to the image
  6. respond on the request with the image url on the cloud storage.


10 - Now you are ready to deploy your project and create post request to save images to "gcs".

11 - If your app in a different domain you need to enable "CORS" on cloud storage using "gsutil" tool

i hope my post is useful for you :)


Monday, July 13, 2015

PyCharm 4.5.3 Full For Windows [With License Key]



Description:
PyCharm 4.5 unites even more tools and features for productive Python, Django and Web development that work together smoothly to offer you a unique coding experience.

Features : 

Screen Shots:


Activation:
- use the provided license key as the following screen shot





Monday, March 2, 2015

What is EDI (Electronic Data Interchange)?

By moving from a paper-based exchange of business document to one that is electronic, businesses enjoy major benefits such as reduced cost, increased processing speed, reduced errors and improved relationships with business partners.

Each term in the definition is significant:

  • Computer-to-computer– EDI replaces postal mail, fax and email. While email is also an electronic approach, the documents exchanged via email must still be handled by people rather than computers. Having people involved slows down the processing of the documents and also introduces errors. Instead, EDI documents can flow straight through to the appropriate application on the receiver’s computer (e.g., the Order Management System) and processing can begin immediately.
A typical manual process looks like this, with lots of paper and people involvement:


The EDI process looks like this — no paper, no people involved:


  • Business documents – These are any of the documents that are typically exchanged between businesses. The most common documents exchanged via EDI are purchase orders, invoices and advance ship notices. But there are many, many others such as bill of lading, customs documents, inventory documents, shipping status documents and payment documents.
  • Standard format– Because EDI documents must be processed by computers rather than humans, a standard format must be used so that the computer will be able to read and understand the documents. A standard format describes what each piece of information is and in what format (e.g., integer, decimal, mmddyy). Without a standard format, each company would send documents using its company-specific format and, much as an English-speaking person probably doesn’t understand Japanese, the receiver’s computer system doesn’t understand the company-specific format of the sender’s format.
There are several EDI standards in use today, including ANSI, EDIFACT, TRADACOMS and ebXML. And, for each standard there are many different versions, e.g., ANSI 5010 or EDIFACT version D12, Release A. When two businesses decide to exchange EDI documents, they must agree on the specific EDI standard and version.
Businesses typically use an EDI translator – either as in-house software or via an EDI service provider – to translate the EDI format so the data can be used by their internal applications and thus enable straight through processing of documents.
  • Business partners – The exchange of EDI documents is typically between two different companies, referred to as business partners or trading partners. For example, Company A may buy goods from Company B. Company A sends orders to Company B. Company A and Company B are business partners.

Saturday, November 8, 2014

dbForge Studio for MySQL Professional Edition V-5.0.67 Full [With Crack]


Description:
dbForge Studio for MySQL is a comprehensive software, designed to work with MySQL , combining features of phpMyAdmin, MySQL Administrator, and other tools for GUI of MySQL .

It works with any database server MySQL from version 3.23 to 5.5 and supports most of the latest features of MySQL , including stored procedures, triggers, views, functions, events, etc. The Devart tool has a unique feature - the stored procedure debugger that helps you find errors in SQL code and correct them.

Here are some key features of " dbForge Studio for MySQL ":
SQL Query Analyzer
Code Completion ( MySQL Intellisense)
Syntax Highlighting
Visual Query Builder
In for quick formation on schema objects
Bezel SQL code ( for mateador code)
Automatic syntax checking on the fly
Database diagram
Schema comparison and synchronization
Object Editor visual scheme
Object Viewer for quick navigation objects MySQL
Window server variables
Security Manager (manage user accounts and privileges)
Session Manager
Service Control for starting and stopping servers MySQL
Wizard maintaining tables and dialogs Flush
Debug Tool .



INSTRUCTIONS FOR APPLYING THE CRACK:

Note: Remember to disable your antivirus during the patching process.

To apply the patch first unzip the files with Winrar or any decompressing that attacks you.
Run dbforgemysql.exe file (this will be the standard Windows installation), then the end of the installation does not run the program.
Enter into the folder named Devart.dbForge.MySQL.v5.0.67.Crack-TPoDT , find three files there:
file_id.diz
Parch.exe
TPoDT.nfo
4. Run the Parch.exe file (if you use Windows 7 or above, run the same as Administrator, right click and click on the option that says "Run as Administrator"), a window will open with a button that says " Patch ", click on it.
5. A new window that will allow you to search for a route, here all you have to do is find where the application was installed usually is here (\ Program Files (x86) \ Devart \ dbForgeStudio for MySQL C) will open
in June. Go to the file named "dbforgemysql.exe" select it and click the open button, a message should appear saying the patch was successful.

Now with that dbForge Studio for MySQL remained ready to use professional tool.



  • if helpful please leave a comment

Sunday, November 2, 2014

What is Functional and non-Functional Requirement ?

Basically, functional requirements describe the features, functioning, and usage of a product/system/software from the perspective of the product and its user. Although referred to as "requirements," they really are a form of design, albeit high-level. Functional requirements also often are called "functional specifications," and "specification" is a synonym for design.

Non-functional requirements are not non-functional at all. Rather, they describe various quality factors, or attributes, which affect the functionality's effectiveness. They do not exist in the abstract but only with respect to relevant functionality. They are often called "ilities," because many end in "ility," such as, usability, reliability, and maintainability.


For instance, if the software doesn't satisfy relevant usability requirements for applicable functional usage, users can't use it appropriately and thus will not achieve the required functioning. Inadequate usability may cause errors which nullify the value of the functioning, such as miscalculating something. Usability difficulties could cause the user not to use (all) the functions necessary to achieve the value, perhaps because they're not able to employ the necessary functions. It may take so long and be so unpleasant to use the software that the user can't use it as much as is needed or even abandons its use entirely.

Saturday, October 18, 2014

Creating First Python Application Using Google App Engine

In this post we will use App Engine services from Google that provides a free playground for us to develop Python web applications. Google App Engine (often referred to as GAE or simply App Engine) is a platform as a service (PaaS) cloud computing platform for developing and hosting web applications in Google-managed data centers. Applications are sandboxed and run across multiple servers. App Engine offers automatic scaling for web applications—as the number of requests increases for an application, App Engine automatically allocates more resources for the web application to handle the additional demand.

1. Creating Google App Engine Application

We need to register our application with your Google account to https://appengine.google.com/. Hit the “Create Application” button and fill everything in the form. Just set to as is in the form if you do not sure what you are doing. I use “hello-app-engine” for the application name, you should change all the name in this toturial to your application name.

2. Creating Local Application

If you are new to AppEngine or GAE, it is better if you use the Google App Engine Launcher desktop application from your computer. Many other people prefer to use the command line that also provided by App Engine. You can find the launcher in the App Engine SDK installation on your hard drive or use comman line appengine_launcher. We need to create a local application using the SDK with the application name we have created before. Click on menu File > Create New Appliation…
There are 4 files generated by the SDK app.yamlfavicon.icoindex.yaml and main.py. The application uses webapp2 as a Python web framework.
File main.py

File app.yaml

The line script: main.app will execute the app in the main.py file. Click on menu Run and Browse, your browser will opens the web application from localhost with ‘Hello world!’ printed on the page.

3. Deploying Application

You will need to deploy the application to the internet. Click the Deploy button and provide your registered email address and password for the Google App Engine. Now you can visit your site http://your-application-name.appspot.com from your browser. Happy coding!