I am looking for way to create simple multiuser Dashboard for OpenStack as alternative to Horizon. Idea is keep Horizon for administrators and manage users in another aplication with possibility to create (with admin confirmation) custom system.
My idea is create a web aplication (Node.js) which would communicate with OpenStack REST API because we need some extra feature (messaging, LDAP/AC Auth).
I also looked for some projects like alternative to Horizon, but cant find anything .
My question is, what is better idea? Create custom solution or use some already created Dashboard(which one?) and only modify it?
Take a look at this open source project:
https://github.com/cyverse/atmosphere
https://github.com/cyverse/troposphere
So its frontend is based on ReactJS and BackboneJS and the backend is the Django and DRF which consumes the OS python client API.
As for your question, it depends. The horizon project has a very good plugin registration service that let you easily create custom dashboards and you don't have to worry about many other details.
However, create a new dashboard on your own also sounds cool but it needs a lot more effort and time than using the horizon.
HTH
Related
I would like to make some Pyton or NodeJS script to help me with repetitive tasks or searchs in my personal Evernote.
I don't want to make any application for general use. Only some scripts for me.
Is there a quick way to make this before creating an account in sandbox.evernote.com? I want to access my already available data in Evernote.
Yes, this exact thing exists. Go here:
https://dev.evernote.com/doc/articles/dev_tokens.php
And get a "developer token" for your production account. It will allow access to your account only and you can do what you like with your data via the API.
I have recently started using Telescope (http://www.telesc.pe/) from the creators of Meteor for a small project. I am just starting to learn about Meteor, and since essentially database / web server and application stack are collapsed into one framework, I'm wondering what the most efficient way is for me to have an external application (for ex: python script) post and access posts/comments from Telescope. Essentially, I'd like a bot to be able to:
Create posts
Add comments to posts
Pull back a list of posts
Ideally I'd like to access this via HTTP requests (get/post/etc), but am not sure how to do this within telescope / meteor or possibly DB queries. Any help (such as an example API call to create a new post) or the appropriate way to do this using Meteor would be much appreciated!
From the documentation it doesn't look like Telescope has a webservice API and there aren't any plans for it on the roadmap either.
Luckily meteor has a packaging system, which telescope already uses a lot.
So you could make a meteor package that hooks into telescope and exposes webservices for the functionality you described.
Meteorpedia has a good article on how to create rest api's in meteor: here
Telescope has a basic API. You can see a sample response here...
http://meta.telesc.pe/api
And here's the package that makes that happen.
https://github.com/TelescopeJS/Telescope/tree/master/packages/telescope-api
You could copy and extend that package to accomplish whatever you need.
I'm wondering if we can provide different views with different URLs in meteor clients with the same server? That is, for a porker game, one view for each player.
A much clear example:
http://app1.meteor.com/myself # a web view for a user
http://app1.meteor.com/all # a web view for the administrator
You can use router. It is very easy to use.
You can find examples on usage here.
Yes. You just need to track user sessions. You can see an example of this here:
http://user-sessions.meteor.com/
and the source can be found here:
http://github.com/possibilities/meteor-user-sessions
I want to develop back-end of iphone app using recess for services layer component. This app will also have web app using same services layer component. I want to develop wep app using some CMS(Drupal) . I m confuse about databases . Since services layer will have its own database and drupal will have its own. But it is never a good idea to use two databases for same application.
Kindly suggest alternatives.
Thanks in advance
Recess allows you to specify which database server to connect to. To accomplish your goal of a shared database, configure Recess to use the same database as Drupal. I recommend at least using a different user account to store your Recess data. That will still allow you to merge/migrate data down the road, should you need it. (Although to me, that sounds highly unlikely.)
Alternatively, consider Recess and Drupal to be different applications, which they are.
I'm not sure I'm asking the right question here, but I'm looking to provide web based functionality from one ASP.NET application to another remote 'portal-like' application. Is it possible to simply give the portal a DLL? As an example, let's say the SaaS web app has a patient-entry form that I want to be able to use from the portal application. I would like the portal app to be able to set preferences (permissions, color, style, etc), make a function call, and have that capability presented within a certain div or something. Is there any .NET technologies that provide this kind of integration?
EDIT:
Here is a link to a quick diagram I made trying to describe the scenario: http://img.ly/ESG. I know there are other ways of doing this (eg JSON-P calls), but I need to give the portal developers something they can control on their end. Also, if anything changes they'll know I will send them a new version of the DLL which will indicate to them the new functionality.
I'll give you a shopping list of things to check out:
DotNetNuke:
http://www.dotnetnuke.com/
Workflow Foundation -
http://msdn.microsoft.com/en-us/netframework/aa663328.aspx
Microsoft SAAS platform -
http://www.microsoft.com/serviceproviders/saas/default.mspx
Depending on exactly what you're looking for, you might also research "multitenancy".
To answer your original question, yes, you can do it with DLL's, but there are easier ways to do it.