I have visited Redis official website and more other platforms for the tutorials but still I am unable to installation of Redis (in-memory data structure store).
The README.md file at Github is also failed to let me complete install and play with Redis.
I am a beginner to Redis and needs some specific and easy guidance in learning or installing it to system and play with it.
You can try Redis University. It provides a Virtual Lab environment for each student. Courses are free. Of course, there are many other tutorials, videos, courses, and books available.
Installation on Windows is not recommended. You have a few options before having to install yourself, if you want just to play with it:
AWS ElastiCache for Redis free for 12 months (cache.t2micro or cache.t3.micro Node, 750 h/month). AWS provides many tutorials as well.
Redis Enterprise Cloud, you choose your favorite cloud for hosting, and it's free up to 30 MB. No CC required.
Redis docker image. You can run it with docker desktop in Mac or Windows as well.
You can try the classic redis-cli to play with it. You can also try some GUI clients available, like RDBTools.
If you are trying to install and facing problems, then post a question with the specifics of what have you tried and what the error you are getting is.
Related
I and a friend want to work on same project but we are in different location.
I will be working on backend while he will be working on frontend.
How do I feed him with my backend API. What's the best solution, app or tools to use.
Strongly recommend using git as a collaboration/version control tool. You can sign up for free at github.com and they now support private repositories. There's a bit of a learning curve, but git is highly adopted and one of the standards for managing code between several 100s or even 1000s of contributors across large projects.
Some of the basics:
1) think of git as a way to share code between developers
2) not only that, but you can manage change history and track changes over time
3) seamlessly manages most changes, enabling you and your team to view point-in-time versions
Check out the Git handbook at https://guides.github.com/introduction/git-handbook/ to get started!
To address your specific question:
when you are ready to share your backend code, check it into your git repository and let your collaborators know that updates are available
make sure to include instructions on how to use your backend code; do they run the server locally? is it deployed to a url? is it running in docker or kubernetes? is it authenticated, and how?
they will "pull" your changes and start working against them; when they have updates, they should commit them to git and push to the remote repository. You can then pull down their changes and review the full frontend/backend solution.
You can use these tools to make your life easier
Github or Bitbucket for code collaboration
Postman or Postwoman for API share
Jira cloud or clubhouse for Issue tracking ( free for 10 users)
Confluence for documentation.
Slack for real time communication.
These are tools I am using for collaboration with others. This is just my opinion.
I have started to try to use the Google Cloud datalab. While I understand it is a Beta product, I find the Doc's very frustrating, to say the least.
The questions here and lack of responses as well as lack of new revisions or docs over the several months the project has been available make me wonder if there is any commitment to the product?
A beginning would be a notebook that shows data ingestion from external sources to both the datastore system and the Big query system. That is a common use case. I'd like to use my own data, it would be great to have a Notebook to ingest it. It seems that should be doable without huge effort? And it would get me (and others) out of this mess trying to link the various terse docs from various products and workspaces up and working together..
in addition to a better explanation of the Git hub connection process (prior question))
For BigQuery, see here: https://github.com/GoogleCloudPlatform/datalab/blob/master/content/datalab/tutorials/BigQuery/Importing%20and%20Exporting%20Data.ipynb
For GCS, see here: https://github.com/GoogleCloudPlatform/datalab/blob/master/content/datalab/tutorials/Storage/Storage%20Commands.ipynb
Those are the only two storage options currently supported in Datalab (which should not be used in any event for large scale data transfers; these are for small scale transfers that can fit in memory in the Datalab VM).
For Git support, see https://github.com/GoogleCloudPlatform/datalab/blob/master/content/datalab/intro/Using%20Datalab%20-%20Managing%20Notebooks%20with%20Git.ipynb. Note that this has nothing to do with Github, however.
As for the low level of activity recently, that is because we have been heads down getting ready for GCP Next (which happens this coming week). Once that is over we should be able to migrate a number of new features over to Datalab and get a new public release out soon.
Datalab isn't running on your local machine. Just the presentation part is in your browser. So if you mean the browser client machine, that wouldn't be a good solution - you'd be moving data from the local machine to a VM which is running the Datalab Python code (and this VM has limited storage space), and then moving it again to the real destination. Instead, you should use the cloud console or (preferably) gcloud command line on your local machine for this.
I have an AngularJS site consuming an API written in Sinatra.
I'm simply trying to deploy these 2 components together on an AWS EC2 instance.
How would one go about doing that? What tools do you recommend? What structure do you think is most suitable?
Cheers
This is based upon my experience of utilizing the HashciCorp line of tools.
Manual: Launch an Ubuntu image, gem install sinatra and deploy your code. Take a snapshot for safe keeping. This one off approach is good for a development box to iron out the configuration process. Write down the commands you run and any options you may need.
Automated: Use the Packer EC2 Builder and Shell Provisioner to automate your commands from the previous manual approach. This will give you a configured AMI that can be launched.
You can apply different methods of getting to an AMI using different toolsets. However, in the end, you want a single immutable image that can be deployed. repeatedly.
I have developed a windows 8 app and I wish to install the app on 10 devices and also when I alter the app I wish to automatically upgrade the app installed on these 10 devices. I do not wish to use the windows store and the app and devices have the necessary certificates needed. Is there a way I can sideload the app to the 10 devices and upgrade the app easily without using a hardrive to uninstall and install the app on each device?
Altough this was asked a while ago i want to answer this, as i myself struggled a long time sideloading LOB-apps and Microsoft almost makes no efforts of clarifying the mess of their licensing programm.
You need to get a sideloading key, you can get it from the microsoft volume licensing center (it is not easy to find, best you ask a distributor partner) costs 100$ and is as far as i know for 25 devices. You need to be partner to obtain such a key.
UPDATE: for unlimited devices (see article posted from user3123726)
FYI: i doubt it but if you plan to have all devices in the same domain you do not need a sideload-key
On the device where the application should run
install the app certificate into 'trusted root certificates' and 'trusted publishers'
install and register the sideloading key
for installing:
/C slmgr /ipk 00000-00000-00000-00000-00000 //your side loading key
for registering:
/C slmgr /ato ec67814b-30e6-4a50-bf7b-d55daf729d1e //for everybody the same key
For publishing and updating the app Microsoft has a service called 'Intune' where you can register your devices and deploy store apps to. I have tried this solution and really couldn't make it work. It worked sometimes but had a lot of crashes and freezes with no usable error message. I highly recommend to write your own update function as i lost many many hours trying to get it to work. It also seems like nobody really is using this solution as it has only 12 reviews in the app store and no forums whatsoever talking about it. However if you wish to try see this link:
https://technet.microsoft.com/en-us/library/dn646972.aspx
You'll need to install the 'Company store app' on each device.
If you tend to write your own update/install mechanism you can use this Powershell command to install the app on the device. You could use dropbox to distribute the packages to the devices and write a service which runs the powershell.
Add-AppxPackage -Path "yourapp.appx" -DependencyPath "Dependencies\x86\appdependency.appx"
I have developed an app in Twilio which I would like to run from the cloud. I tried learning about AWS and Google App Engine but am quite confused at this stage:
I have 2 questions which I hope to get your help on:
1) How can I store my scripts and database in the cloud? Right now, everything is running out of my local machine but I would like to transfer the scripts and db to another server and run my app at a predetermined time of day. What would be the best way to do this?
2) How can I write a batch file to run my app at a predetermined time of day in the cloud?
I understand this does not have code, but I really hope someone can point me to the right direction. I have spent lots of time trying to understand this myself but still am unsure. Tks in adv.
Update: The application is a Twilio app that makes calls to people, the script simply applies an algorithm to make calls in a certain fashion and the database is a mysql db that provides the details of people to be called.
This is quite difficult to provide an exact answer without understanding what is the application, what is the DB or what is the script that you wish to run.
I can give you a couple of ideas that might be helpful in such cases.
OpsWorks (http://aws.amazon.com/opsworks/) is a managed service for managing applications. You can define your stack (multiple layers like web, workers, DB...) and what are the chef recipes that should run in various points in the life of the instances in each layer (startup, shutdown, app deployment or stack modification..). Then you can use the ability to add instances to each layer in specific days and hours, to implement the functionality of running at predetermined times as you requested.
In such a solution you can either have some of your instances (like DB) always on, or even to bootstrap them using the chef recipes every day, with restore from snapshot on start and create snapshot on shutdown.
Another AWS service that you use is Data Pipeline (http://aws.amazon.com/datapipeline/). It is designed to move data periodically between data sources, for example from a MySQL database to Amazon Redshift, the Data warehouse service. But you can use it to trigger scripts and run random shell scripts that you wish (http://docs.aws.amazon.com/datapipeline/latest/DeveloperGuide/dp-object-shellcommandactivity.html), and schedule it to run in various conditions like every hour/day or specific times (http://docs.aws.amazon.com/datapipeline/latest/DeveloperGuide/dp-concepts-schedules.html).
A simple path here would be just to create an EC2 instance in AWS, and put the components needed to run your app there. A thorough walk through is here:
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/get-set-up-for-amazon-ec2.html
Essentially you will create an EC2 virtual machine, which you can for most purposes treat just like any other Linux server. You can install MySQL on it, copy your script there, and run it. Of course whatever container or support libraries your code requires will need to be installed as well.
You don't say what OS you are using locally, but if it is Mac or Linux, you should be able to follow almost the same process to get your script running on an EC2 instance that you used on your local machine.
As you get to know AWS, there are sophisticated services you can use for deployment, infrastructure orchestration, database services, and so on. But just to get started running a script from a virtual machine should be pretty straightforward.
I recently developed a Twilio application using Ruby on Rails for the backend and found Heroku extremely simple to setup and launch. While Heroku does cost more than AWS, I found that the time I saved using Heroku more than made up this. As an early stage startup, we wanted to spend our time developing important features, and not "wasting" time optimizing our AWS cloud.
However, while I believe Heroku is ideal for early-stage websites/startups I do believe hosting should be reevaluated once a company reaches a certain size. At some point it becomes economically viable to devote resources into optimizing an AWS cloud solution because it will be cheaper than Heroku in the long run.