I am checking to see if there are any recommendations on creating a multisite instance of the Symfony CMF.
My initial thoughts are to launch with Symfony 2.2 and would like to rapidly adopt the CMF once it becomes stable. If there are any known best practices to allow this, please let me know.
The CMF for now has no special support for multisite. The route document however does map the hostname field so multi-domain routing should already work.
Unless you want to mix the routes from all domains, you would want to separate the routes tree by domain and build something into the route provider to handle the domain name. A pull request on the cmf RoutingBundle would definitely be appreciated.
Related
I have an app in Amplify that currently has a custom domain attached. I can access the app fine, all seems to be working good on this, but I just tried accessing the default Amplify subdomain (master.something.amplifyapp.com) and this works also.
I would like to either remove this subdomain or redirect it to the custom domain so that users can only access the app from the custom URL.
Looked through documentation, other questions online and cannot seem to find anything related to this. I only found a delete-domain-association page, but unsure if this is actually the way to do it https://awscli.amazonaws.com/v2/documentation/api/latest/reference/amplify/delete-domain-association.html
Below is how the app looks in domain management:
Is there a best practice on how this should be done? Should it be redirected, should it be removed or something completely different?
Thank you! I appreciate any comment
I have tried looking for similar questions and through documentation.
I am new to Symfony and Sylius, and I have installed Sylius which is installed as a symfony "vendor" bundle by default.
I have moved the route to Sylius (which is accessible by default at "/") to "/shop", and I will developp myself the home page and other pages (not related to the shop, like information pages, etc.)
But, I need authentication in these other pages to manage user accounts (with data not related to the shop).
What I would like is a shared authentication system, but I don't know if it is possible to use Sylius' one and how to do this.
Thanks for you help !
Jon
THis is related to Symfony, you will need to override security in way to share context - your app and Sylius. Then some parts of Sylius will be locked as now.
http://symfony.com/doc/current/security.html
What I have made is route my Bundle under "/admin/blog". As my route is under /admin, I have to authenticate with the Sylius authentication, and it Seems to work well ! :-)
The future development of my symfony2 project
( which is actually more or less a static website with an authentification system )
would be to provide authentified users a CMS to easily edit text and images / import files / create pages / give acces to their pages as the website grows and evolves.
I have been thinking implementing my project with Drupal would be way forward .
how can i proceed ?
Is doing the reverse better?
what are other options?
I am not sure what you mean by 'the reverse', but there is a Symfony module available for D7. I would suggest setting up a Drupal test bed and seeing about integrating your site into drupal.
It is my understanding that Symfony2 has gone into core in D8, but D8 is probably a long way from initial release.
We have a 5 years old system built by Drupal 5. It is not a small system (about 50K lines of code), and most of the functionality has nothing to do with 'content management'.
For this reason, we're thinking about integrating Symfony2 to our current system. The ideal is to keep using the current code for current functionality while developing new features with Symfony2. Slowly we'll move more and more pieces of code from Drupal to Symfony.
My question is how do you suggest implementing this? I though about the following approaches:
Create a module in Drupal. This module will contain the Symfony files and will load the class loader of Symfony. Someone has done this before? are there some critical things I should be aware of?
Create a separate installation of Symfony and hopefully create a different vhost record which point to certain pages in the website. As far as I know I can configure vhost to be a sub-host of my current host (e.g. mysymfony.mydrupal.com). But I can't configure it to point to a specific path in the same domain (mydrupal.com/mysymfony.php). is this true? In this approach the performance would be better for those pages that use Symfony, since it won't need the Drupal bootstrap.
Any other suggestions?
Thanks!
Be aware that you'll likely have to upgrade your PHP version on the machine running Drupal if you'd like to run Symfony2 on the same machine (anything under 5.3.8 and the configurator will object). You may also want to hold out for a bit if you want to stick with Drupal - Drupal 8 is integrating Symfony2 components. Also, there exists (in beta form anyhow), a content management framework for Symfony2.
Regarding vhosts, you are correct - you point a vhost to a directory, not a file. You could however create a rewrite rule to redirect to a specific page, if you wanted (check out the .htaccess file included in the web/ directory in a Symfony distribution - by default it redirects requests to app.php).
Because I'm new here I can't have more than two links in a post. I was also going to say:
I would start rewriting core functionality (users, permissions, etc) if none of the existing bundles meet your needs. As well as searching github, you could try knpbundles.com to find bundles that solve similar problems.
I have two instances of Drupal on same server instance 1 and instance 2 with different databases. I want to do following functionality so I will go ahead for my work.
Unique login for both instances. When I login to instance 1 then if I open url of instance 2 on same browser then it should not ask for me login.
While any add/update operation perform on instance 1 or instance 2 then user table should be updated in both databases.
Please let me know so I will go ahead.
Thanks in advance.
If there you I would utilize Drupal`s openid (oAuth) technologies. That could be done with some minor coding or even a couple of modules.
That would allow you to create linked accounts but different profiles for each site. You would have a setup like it is here at stackexchange network and some additional functionality.
EDIT: There is a module called OpenID URL.It will give your users ability to use their profile pages as OpenID URLs. You could do it with a just a tad of coding.
Then you could simply copy "Loin with OpenID" URL form your other site and name it "Create joined account..." or something like that.
You could use oAuth technology if you want more advanced connections.
There is also a possibility to create a multisite website.
I have not tried this module yet, but it sounds promising, to solving your first part of the problem: project bakery.
Bakery provides a "single sign on" feature for Drupal based sites that
are on the same second-level domain (i.e. example.com,
subsite.example.com, subsite2.example.com). It could also provide
support for any other website that implements the same web cookie,
xmlrpc, and POST methods.
For the second part I'm very interested in a solution. The only thing I can come up with at the moment, is some kind of RSS feeds. I know you can create nodes based on that.