You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to be able to clone this repo into a new directory and have it accessible as the index of that directory. Then the <head> of the sites with which I use this could simply reference <link rel="token_endpoint" href="https://example.com/token/">, rather than <link rel="token_endpoint" href="https://example.com/token/endpoint.php">.
The text was updated successfully, but these errors were encountered:
I considered this before making the suggestion. If you're manually copying the file into a different directory, then renaming the file in the process of copying it does not add much burden. Unless the directory into which you copy it is not version controlled, AND that directory has an index.php, AND you accidentally forget to change the name, then there's not much risk here. If a user copies this index.php over a different index.php, well ... I hope they have backups!
I'd love to have this live in the same directory as selfauth, but I do not want to manually copy files around. If this file were migrated to the selfauth repo (and, perhaps, named token.php), it would make this all a bit easier (for me).
Feel free to close this issue if you wish. It's not a big deal to me either way.
After a good night of thinking, I might be coming around to this.
I was looking at possibly streamlining the installation through composer (composer create-project), and that too always wants to install into an empty folder. Much like git.
If all the tooling people are likely to use are creating new folders, I may as well rename it index.
Zegnat
changed the title
Rename endpoint.php to index.php?
Rename endpoint.php to index.php
May 22, 2018
It would be nice to be able to clone this repo into a new directory and have it accessible as the index of that directory. Then the
<head>
of the sites with which I use this could simply reference<link rel="token_endpoint" href="https://example.com/token/">
, rather than<link rel="token_endpoint" href="https://example.com/token/endpoint.php">
.The text was updated successfully, but these errors were encountered: